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: 0ae1470a892abf6c30f6b6d8eaa945e4e4678f1620137130d109bea4c9ddae88
Tx prefix hash: 1f2a0a51e78d517baf8b61e1f2804068d5c7f6edcae0e93e0fe294fadfcc1f6d
Tx public key: e33063bbf6b2bd7619b5df55a48a6996887e4396fc96c503497ff9b7d4fa46d0
| Timestamp: 1779642270 | Timestamp [UTC]: 2026-05-24 17:04:30 | Age [y:d:h:m:s]: 00:015:11:28:32 |
| Block: 1382 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6646 | RingCT/type: yes/0 |
| Extra: 01e33063bbf6b2bd7619b5df55a48a6996887e4396fc96c503497ff9b7d4fa46d0020900000002ba6d17be00 | ||
1 output(s) for total of 35.091816610815 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7db9e6f357b1dda301403703a7fdffc36481ce04ea4973a4ed66d2e2b6ced929 | 35.091816610815 | 1532 of 0 | <c5> |
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": 1442,
"vin": [ {
"gen": {
"height": 1382
}
}
],
"vout": [ {
"amount": 35091816610815,
"target": {
"tagged_key": {
"key": "7db9e6f357b1dda301403703a7fdffc36481ce04ea4973a4ed66d2e2b6ced929",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 227, 48, 99, 187, 246, 178, 189, 118, 25, 181, 223, 85, 164, 138, 105, 150, 136, 126, 67, 150, 252, 150, 197, 3, 73, 127, 249, 183, 212, 250, 70, 208, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}