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: 24513114353d4272153b2414c3decaaf0fd23ef0e3c07688b9c735beb0305170
Tx prefix hash: 571e077e52f6fa8b5707a3a3e3f37ea0dd91ad8474b34e0f9ba116bdacc08655
Tx public key: 9e755f1a6c5c4c52e852da55ef49baee19b01fd9b75d0b9bdeac1d65a5f21a3b
| Timestamp: 1780735713 | Timestamp [UTC]: 2026-06-06 08:48:33 | Age [y:d:h:m:s]: 00:002:14:30:20 |
| Block: 6363 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1523 | RingCT/type: yes/0 |
| Extra: 019e755f1a6c5c4c52e852da55ef49baee19b01fd9b75d0b9bdeac1d65a5f21a3b020900000005e49593ff00 | ||
1 output(s) for total of 34.760005050651 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd3742f78f73746d1f5cd6831ffbe825834e9d9b5f250c7cb9937c33d8b8a139 | 34.760005050651 | 7852 of 0 | <bc> |
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": 6423,
"vin": [ {
"gen": {
"height": 6363
}
}
],
"vout": [ {
"amount": 34760005050651,
"target": {
"tagged_key": {
"key": "fd3742f78f73746d1f5cd6831ffbe825834e9d9b5f250c7cb9937c33d8b8a139",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 158, 117, 95, 26, 108, 92, 76, 82, 232, 82, 218, 85, 239, 73, 186, 238, 25, 176, 31, 217, 183, 93, 11, 155, 222, 172, 29, 101, 165, 242, 26, 59, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}