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: 456130ec16b2932653c4a1e487abca0ef485e65f1740a36e77382a56b75860b0
Tx prefix hash: 61fc47f164a8d621428d7db5cd62d691ca75b1173f5466e4814e7c79819bdf18
Tx public key: 07003b3cabfb88c02929969d361397328cb8a59bf6ebb49c692c57c67c66f94b
| Timestamp: 1780700641 | Timestamp [UTC]: 2026-06-05 23:04:01 | Age [y:d:h:m:s]: 00:003:04:46:57 |
| Block: 6048 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1905 | RingCT/type: yes/0 |
| Extra: 0107003b3cabfb88c02929969d361397328cb8a59bf6ebb49c692c57c67c66f94b020900000001e49593ff00 | ||
1 output(s) for total of 34.780895671797 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5effc142beff400a022f1d08045fa9eb270e91c64d1faa97ef87ac24f3733ef6 | 34.780895671797 | 7517 of 0 | <47> |
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": 6108,
"vin": [ {
"gen": {
"height": 6048
}
}
],
"vout": [ {
"amount": 34780895671797,
"target": {
"tagged_key": {
"key": "5effc142beff400a022f1d08045fa9eb270e91c64d1faa97ef87ac24f3733ef6",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 7, 0, 59, 60, 171, 251, 136, 192, 41, 41, 150, 157, 54, 19, 151, 50, 140, 184, 165, 155, 246, 235, 180, 156, 105, 44, 87, 198, 124, 102, 249, 75, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}