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: 403116030de16a90189a88c27798abb9405f358fc99a44e8e2a688930994e9c0
Tx prefix hash: 5192e5beae0199fde0298a0bc3cb4e5a7687b198aa1e0c85b1a65f7ce9f64073
Tx public key: dbd1d2636b93350ef907121aa19db2faab7765f25b8dc85ff5736bee7b6f0905
| Timestamp: 1780706110 | Timestamp [UTC]: 2026-06-06 00:35:10 | Age [y:d:h:m:s]: 00:003:03:15:48 |
| Block: 6110 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1856 | RingCT/type: yes/0 |
| Extra: 01dbd1d2636b93350ef907121aa19db2faab7765f25b8dc85ff5736bee7b6f0905020900000001e49593ff00 | ||
1 output(s) for total of 34.776782874844 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1823e37f0f8094c436776a2a23251715e62272fac0e254912a35196bc612ee80 | 34.776782874844 | 7583 of 0 | <88> |
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": 6170,
"vin": [ {
"gen": {
"height": 6110
}
}
],
"vout": [ {
"amount": 34776782874844,
"target": {
"tagged_key": {
"key": "1823e37f0f8094c436776a2a23251715e62272fac0e254912a35196bc612ee80",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 219, 209, 210, 99, 107, 147, 53, 14, 249, 7, 18, 26, 161, 157, 178, 250, 171, 119, 101, 242, 91, 141, 200, 95, 245, 115, 107, 238, 123, 111, 9, 5, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}