I'm having troubles finding the payment ID in a transaction info. I'm using the daemon RPC API to get the transaction info. According to the official documentation the extra
field is used for the payment ID. However, It seems like this byte array is not even the size of a valid payment ID (8 or 32 bytes).
Here are two examples:
- tx hash:
c748fedd286bdd5a34e223316593625cd4482d7666b262cef51f8bc0e1694b26
'extra' field (in hex):012772e8e0893433644b93401067a804415d86ddde4c91154a95c84a365111fb86022100fb7ef3f11937667a9242ed4d252ed97c4401079bc11d87a17a581032bcb02769
(68 bytes) - tx hash:
b9678d96071be7d31484c324d2009848872744e79ddd85eb94b71fb867b543cb
'extra' field (in hex):01ed37fc961021099a74c227fa414c29a7213e6678215abf5f37a1c25ed4bd26a2
(33 bytes)
I have another transaction without payment ID (shows 0000000000000000
in the cli wallet) but the extra
field in this transaction is not filled with 0's, but actually looks random (I'm not posting its details for privacy reasons).
So what exactly is in the extra
field, and how do I find the payment ID in the transaction info?