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: 343e10a06629a1d4c9b6663505ad4c07ddffe65bf12fc66d6c54c115cc8fcc3e
Tx prefix hash: 46f3a391b857bb72d35bf0d90c7026f8b4a30e33d77f69add52faeacb6442d1d
Tx public key: 53f68e83b7447c67fdc409e1a2597a310e34f3fedb6eaa593e2bf671cee63feb
| Timestamp: 1780824689 | Timestamp [UTC]: 2026-06-07 09:31:29 | Age [y:d:h:m:s]: 00:001:11:40:38 |
| Block: 7236 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 650 | RingCT/type: yes/0 |
| Extra: 0153f68e83b7447c67fdc409e1a2597a310e34f3fedb6eaa593e2bf671cee63feb020900000002e49593ff00 | ||
1 output(s) for total of 34.709606538563 HMNY
| stealth address | amount | amount idx | tag |
| 00: f80b46728aff8ca541de961f17edaafce2edf30b225aac4240fb0eae057960b2 | 34.709606538563 | 8910 of 0 | <69> |
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": 7296,
"vin": [ {
"gen": {
"height": 7236
}
}
],
"vout": [ {
"amount": 34709606538563,
"target": {
"tagged_key": {
"key": "f80b46728aff8ca541de961f17edaafce2edf30b225aac4240fb0eae057960b2",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 83, 246, 142, 131, 183, 68, 124, 103, 253, 196, 9, 225, 162, 89, 122, 49, 14, 52, 243, 254, 219, 110, 170, 89, 62, 43, 246, 113, 206, 230, 63, 235, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}