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: 0f753a872ba5464c32150180fe7c3ad05d7bda3ac4c416e4239efe8a41db2297
Tx prefix hash: 447832c965895371f3a7e769d26e00bc3c8d1e6009f5447f7afbb865d502ce63
Tx public key: 6322d057c2669f33b032c68a0fa8847455ce48aa50e25c8bab053a5b4feea537
| Timestamp: 1780066704 | Timestamp [UTC]: 2026-05-29 14:58:24 | Age [y:d:h:m:s]: 00:010:10:37:33 |
| Block: 4594 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3292 | RingCT/type: yes/0 |
| Extra: 016322d057c2669f33b032c68a0fa8847455ce48aa50e25c8bab053a5b4feea53702090000000226697be300 | ||
1 output(s) for total of 34.882505372801 HMNY
| stealth address | amount | amount idx | tag |
| 00: 92a98ce3428e00802cfbf74beade5ded9073f680a4d024d0aed1918171e234bf | 34.882505372801 | 5766 of 0 | <ee> |
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": 4654,
"vin": [ {
"gen": {
"height": 4594
}
}
],
"vout": [ {
"amount": 34882505372801,
"target": {
"tagged_key": {
"key": "92a98ce3428e00802cfbf74beade5ded9073f680a4d024d0aed1918171e234bf",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 99, 34, 208, 87, 194, 102, 159, 51, 176, 50, 198, 138, 15, 168, 132, 116, 85, 206, 72, 170, 80, 226, 92, 139, 171, 5, 58, 91, 79, 238, 165, 55, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}