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: 73a7ba5fdfba37f08efea2d78daa59a4756888e7080c94d0439c63fdd9c2d628
Tx prefix hash: 61f8ba64d9a9d2562c5293006c596fa6808540d118fac757e5b00c79c966dd2b
Tx public key: 56b0dfc4fcbcb1856d4167c8f57e65558bc281784ac00b70031dc9fc836f5344
| Timestamp: 1780042053 | Timestamp [UTC]: 2026-05-29 08:07:33 | Age [y:d:h:m:s]: 00:019:00:14:46 |
| Block: 4298 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4447 | RingCT/type: yes/0 |
| Extra: 0156b0dfc4fcbcb1856d4167c8f57e65558bc281784ac00b70031dc9fc836f534402090000000426697be300 | ||
1 output(s) for total of 34.897183515171 HMNY
| stealth address | amount | amount idx | tag |
| 00: 67cc937582e6876d46090ae16f594412e7e1c5b53d91f282d209f8071f1fbff6 | 34.897183515171 | 5370 of 0 | <33> |
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": 4358,
"vin": [ {
"gen": {
"height": 4298
}
}
],
"vout": [ {
"amount": 34897183515171,
"target": {
"tagged_key": {
"key": "67cc937582e6876d46090ae16f594412e7e1c5b53d91f282d209f8071f1fbff6",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 86, 176, 223, 196, 252, 188, 177, 133, 109, 65, 103, 200, 245, 126, 101, 85, 139, 194, 129, 120, 74, 192, 11, 112, 3, 29, 201, 252, 131, 111, 83, 68, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}