For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 218c2f793331b2dde550ff8fc96008708f9d64f17d3924bd24278ec3fb5874e5
Tx prefix hash: 48872e7839ff536817e92b2d88320c6f7dd41b186be3cc7b83e66560a3a2f4bc
Tx public key: 1e50e6231982b9f95f9ead468f0789410d3dc42b38265308a44599de7902259c
| Timestamp: 1780717012 | Timestamp [UTC]: 2026-06-06 03:36:52 | Age [y:d:h:m:s]: 00:002:18:47:57 |
| Block: 6207 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1679 | RingCT/type: yes/0 |
| Extra: 011e50e6231982b9f95f9ead468f0789410d3dc42b38265308a44599de7902259c020900000002e49593ff00 | ||
1 output(s) for total of 34.770349313293 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ec15c488ea479d6f69ea8a9b4cc9126089d7f118de5775496a66ca8516c455c | 34.770349313293 | 7686 of 0 | <0a> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 6267,
"vin": [ {
"gen": {
"height": 6207
}
}
],
"vout": [ {
"amount": 34770349313293,
"target": {
"tagged_key": {
"key": "4ec15c488ea479d6f69ea8a9b4cc9126089d7f118de5775496a66ca8516c455c",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 30, 80, 230, 35, 25, 130, 185, 249, 95, 158, 173, 70, 143, 7, 137, 65, 13, 61, 196, 43, 56, 38, 83, 8, 164, 69, 153, 222, 121, 2, 37, 156, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}