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: b70f358f29c501207f78d24bdc260c455dcdf2ac69f6b2c23d894a23f1d66f72
Tx prefix hash: a366d89e692878b9c1fd41d47b24d7f47a0f1d33c33dd1d5b5c83351fe1d5fb6
Tx public key: bc54ec86f1da5fdc595ff3d2aa48c91a32ae8e0fc3a9409df59ccacc0df0d554
| Timestamp: 1780737252 | Timestamp [UTC]: 2026-06-06 09:14:12 | Age [y:d:h:m:s]: 00:002:16:21:45 |
| Block: 6373 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1513 | RingCT/type: yes/0 |
| Extra: 01bc54ec86f1da5fdc595ff3d2aa48c91a32ae8e0fc3a9409df59ccacc0df0d554020900000002e49593ff00 | ||
1 output(s) for total of 34.759342061860 HMNY
| stealth address | amount | amount idx | tag |
| 00: 62ef88458678fc5deb06a7380429d70f46e59d03623aa5d4a54db1d1b1531369 | 34.759342061860 | 7862 of 0 | <1c> |
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": 6433,
"vin": [ {
"gen": {
"height": 6373
}
}
],
"vout": [ {
"amount": 34759342061860,
"target": {
"tagged_key": {
"key": "62ef88458678fc5deb06a7380429d70f46e59d03623aa5d4a54db1d1b1531369",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 188, 84, 236, 134, 241, 218, 95, 220, 89, 95, 243, 210, 170, 72, 201, 26, 50, 174, 142, 15, 195, 169, 64, 157, 245, 156, 202, 204, 13, 240, 213, 84, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}