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: 530745b131e00025845a11c9d92719e9b8598c3a747dd3b356593970a06fa8ad
Tx prefix hash: a1cba62b3d88e7f103a74ab154a4558603d3f10479cc0f4b857ee4ec3b2288a1
Tx public key: a79ea8b15748563797e9e1a0dcb67d32b6c9e8ba27a26bb5e407c08bd43463f2
| Timestamp: 1779429924 | Timestamp [UTC]: 2026-05-22 06:05:24 | Age [y:d:h:m:s]: 00:017:14:02:47 |
| Block: 4 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0791 kB |
| Tx version: 2 | No of confirmations: 7882 | RingCT/type: yes/0 |
| Extra: 01a79ea8b15748563797e9e1a0dcb67d32b6c9e8ba27a26bb5e407c08bd43463f2 | ||
1 output(s) for total of 35.184170762737 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c17edfd8c225c6b597262594f910d8cb050aacb1ef6240f1ac6701024c2d878 | 35.184170762737 | 0 of 0 | - |
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": 64,
"vin": [ {
"gen": {
"height": 4
}
}
],
"vout": [ {
"amount": 35184170762737,
"target": {
"key": "5c17edfd8c225c6b597262594f910d8cb050aacb1ef6240f1ac6701024c2d878"
}
}
],
"extra": [ 1, 167, 158, 168, 177, 87, 72, 86, 55, 151, 233, 225, 160, 220, 182, 125, 50, 182, 201, 232, 186, 39, 162, 107, 181, 228, 7, 192, 139, 212, 52, 99, 242
],
"rct_signatures": {
"type": 0
}
}