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: 67a50fda6d3d38e60b2808799f5bc7cc22557bdb65b259b6867cfbd76d05079b
Tx prefix hash: a02c075f4a8da1583de9beb767fa95b3a290021d28992e0624b0a4541769363d
Tx public key: d4697b8b51e3337a24a429ee21150f41af09dfe0b91f060e8bc539636e7ac0c3
| Timestamp: 1779460482 | Timestamp [UTC]: 2026-05-22 14:34:42 | Age [y:d:h:m:s]: 00:017:12:05:54 |
| Block: 432 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7464 | RingCT/type: yes/0 |
| Extra: 01d4697b8b51e3337a24a429ee21150f41af09dfe0b91f060e8bc539636e7ac0c302090000000193369e7d00 | ||
1 output(s) for total of 35.155460026447 HMNY
| stealth address | amount | amount idx | tag |
| 00: 06c17d072a75241f654343d5603cf7def69b3552c9a7f8b29a17967661568622 | 35.155460026447 | 436 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": 492,
"vin": [ {
"gen": {
"height": 432
}
}
],
"vout": [ {
"amount": 35155460026447,
"target": {
"tagged_key": {
"key": "06c17d072a75241f654343d5603cf7def69b3552c9a7f8b29a17967661568622",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 212, 105, 123, 139, 81, 227, 51, 122, 36, 164, 41, 238, 33, 21, 15, 65, 175, 9, 223, 224, 185, 31, 6, 14, 139, 197, 57, 99, 110, 122, 192, 195, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}