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: 4012e583c5d8e6a3801d499a3038479b39089bdc5e9289386815074daf7819a7
Tx prefix hash: b303c0c2180e959e64c417e21b7b67f23bd1f46bd49a510190b0b7a1010160f4
Tx public key: ba96d64f38faee92168f3d4090ec158d0b99ef241cf98a69b4421ca06f67f964
| Timestamp: 1780814169 | Timestamp [UTC]: 2026-06-07 06:36:09 | Age [y:d:h:m:s]: 00:001:16:42:44 |
| Block: 7027 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 859 | RingCT/type: yes/0 |
| Extra: 01ba96d64f38faee92168f3d4090ec158d0b99ef241cf98a69b4421ca06f67f964020900000001e49593ff00 | ||
1 output(s) for total of 34.716010040418 HMNY
| stealth address | amount | amount idx | tag |
| 00: e77441835f2dd4b247fa47d3654b665876b00ff1874ab39a576868c8b428762d | 34.716010040418 | 8667 of 0 | <9b> |
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": 7087,
"vin": [ {
"gen": {
"height": 7027
}
}
],
"vout": [ {
"amount": 34716010040418,
"target": {
"tagged_key": {
"key": "e77441835f2dd4b247fa47d3654b665876b00ff1874ab39a576868c8b428762d",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 186, 150, 214, 79, 56, 250, 238, 146, 22, 143, 61, 64, 144, 236, 21, 141, 11, 153, 239, 36, 28, 249, 138, 105, 180, 66, 28, 160, 111, 103, 249, 100, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}