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: 52eb18c05c2a29ab85e58162c8c68e9fd2d522eb091af444e21ae8a5291a0e4f
Tx prefix hash: 9533254aa6d1ebc1f4c1ecf12409c36a274cb236822df9c62aea2dbcb6ae2d84
Tx public key: 37128a711b1915cf8071db5ad82a23d3fc20a32851ba80ae54c2dfbbcb024f59
| Timestamp: 1780016354 | Timestamp [UTC]: 2026-05-29 00:59:14 | Age [y:d:h:m:s]: 00:019:07:23:05 |
| Block: 4121 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4624 | RingCT/type: yes/0 |
| Extra: 0137128a711b1915cf8071db5ad82a23d3fc20a32851ba80ae54c2dfbbcb024f5902090000000c26697be300 | ||
1 output(s) for total of 34.911586429186 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d0ded5d6d3c8e64768a06a4bc24dc89fe402cde9f7f503f2a9f639623482b0e | 34.911586429186 | 5140 of 0 | <a8> |
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": 4181,
"vin": [ {
"gen": {
"height": 4121
}
}
],
"vout": [ {
"amount": 34911586429186,
"target": {
"tagged_key": {
"key": "3d0ded5d6d3c8e64768a06a4bc24dc89fe402cde9f7f503f2a9f639623482b0e",
"view_tag": "a8"
}
}
}
],
"extra": [ 1, 55, 18, 138, 113, 27, 25, 21, 207, 128, 113, 219, 90, 216, 42, 35, 211, 252, 32, 163, 40, 81, 186, 128, 174, 84, 194, 223, 187, 203, 2, 79, 89, 2, 9, 0, 0, 0, 12, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}