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: 235cf24915a5f841bccf1da306422b1ef4e5e6563885c69e80a8d2f63398adad
Tx prefix hash: e8b6144fafb58f88254f9ace733f359adf5f3a80f51f07a1d21f33b53a96733b
Tx public key: e9c9ee215ab6cbcb943de1cab1dd5ee00fca2c2c91a95c8da444e91fa07ce27c
| Timestamp: 1781025555 | Timestamp [UTC]: 2026-06-09 17:19:15 | Age [y:d:h:m:s]: 00:006:03:07:43 |
| Block: 8736 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 9 | RingCT/type: yes/0 |
| Extra: 01e9c9ee215ab6cbcb943de1cab1dd5ee00fca2c2c91a95c8da444e91fa07ce27c020900000002e49593ff00 | ||
1 output(s) for total of 34.603031819840 HMNY
| stealth address | amount | amount idx | tag |
| 00: ed71f4b123bfb45e47777e4f3c59d40eb4d6e93ded98ae9ce842a50cbff6bafc | 34.603031819840 | 10806 of 0 | <56> |
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": 8796,
"vin": [ {
"gen": {
"height": 8736
}
}
],
"vout": [ {
"amount": 34603031819840,
"target": {
"tagged_key": {
"key": "ed71f4b123bfb45e47777e4f3c59d40eb4d6e93ded98ae9ce842a50cbff6bafc",
"view_tag": "56"
}
}
}
],
"extra": [ 1, 233, 201, 238, 33, 90, 182, 203, 203, 148, 61, 225, 202, 177, 221, 94, 224, 15, 202, 44, 44, 145, 169, 92, 141, 164, 68, 233, 31, 160, 124, 226, 124, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}