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: 17418a3936efa720d64001b09b187f6a491bf3ac4b9630039e3a2f1fdf8034a4
Tx prefix hash: a325194b96dc47008297550e998023cb10ca66fd66f13d626aec9999cebb3d88
Tx public key: 567441094bbf897e28acff40a1fb0a3f8ce7557da22cf6ce7bc977e7a9dc6983
| Timestamp: 1780322757 | Timestamp [UTC]: 2026-06-01 14:05:57 | Age [y:d:h:m:s]: 00:007:11:30:00 |
| Block: 5016 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2870 | RingCT/type: yes/0 |
| Extra: 01567441094bbf897e28acff40a1fb0a3f8ce7557da22cf6ce7bc977e7a9dc698302090000003e26697be300 | ||
1 output(s) for total of 34.849425312552 HMNY
| stealth address | amount | amount idx | tag |
| 00: 210e19a6ee258ab21091a993dd6822497d57f3e0e6decfa4da840bf26c7a71b8 | 34.849425312552 | 6389 of 0 | <5f> |
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": 5076,
"vin": [ {
"gen": {
"height": 5016
}
}
],
"vout": [ {
"amount": 34849425312552,
"target": {
"tagged_key": {
"key": "210e19a6ee258ab21091a993dd6822497d57f3e0e6decfa4da840bf26c7a71b8",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 86, 116, 65, 9, 75, 191, 137, 126, 40, 172, 255, 64, 161, 251, 10, 63, 140, 231, 85, 125, 162, 44, 246, 206, 123, 201, 119, 231, 169, 220, 105, 131, 2, 9, 0, 0, 0, 62, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}