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: 855edd5f952ad34912317a1e47eaa7f578fa99cf3b0f7ddf3b9869de339d1e56
Tx prefix hash: f7cd42c9babce8411fd003cfa93b83d995372ccc0cdfd408225be9cb491190f9
Tx public key: 0ec7fb468817a756c15f67968b63ccfbe6873c6f4b545523a76264ddb1f5dae2
| Timestamp: 1779647926 | Timestamp [UTC]: 2026-05-24 18:38:46 | Age [y:d:h:m:s]: 00:015:04:40:07 |
| Block: 1463 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6423 | RingCT/type: yes/0 |
| Extra: 010ec7fb468817a756c15f67968b63ccfbe6873c6f4b545523a76264ddb1f5dae2020900000002ba6d17be00 | ||
1 output(s) for total of 35.086395505820 HMNY
| stealth address | amount | amount idx | tag |
| 00: c9e63476ae7dabe532731c48adf0e1669216dd443fab1227c937926607cedf4a | 35.086395505820 | 1617 of 0 | <e2> |
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": 1523,
"vin": [ {
"gen": {
"height": 1463
}
}
],
"vout": [ {
"amount": 35086395505820,
"target": {
"tagged_key": {
"key": "c9e63476ae7dabe532731c48adf0e1669216dd443fab1227c937926607cedf4a",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 14, 199, 251, 70, 136, 23, 167, 86, 193, 95, 103, 150, 139, 99, 204, 251, 230, 135, 60, 111, 75, 84, 85, 35, 167, 98, 100, 221, 177, 245, 218, 226, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}