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: 08830b0787ec63e5ce13a872e8879a7c074d1765271b4ef55cdfaf353cbc4c59
Tx prefix hash: 374d6e28c8caf649c91cb64e4c2c4ee53a5f0ad0eee1d332cd19072206fc7d5d
Tx public key: 45ffaeddd792362f75f809cd0e98b6c3d89d3c302aa12ef7e5f2dc9353be9e93
| Timestamp: 1780765437 | Timestamp [UTC]: 2026-06-06 17:03:57 | Age [y:d:h:m:s]: 00:002:06:14:56 |
| Block: 6611 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1275 | RingCT/type: yes/0 |
| Extra: 0145ffaeddd792362f75f809cd0e98b6c3d89d3c302aa12ef7e5f2dc9353be9e93020900000001e49593ff00 | ||
1 output(s) for total of 34.743566660013 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1dd9692f1b5570916a25cf63695e20df8fd8cc21fb8649c4b356a3351a0d7748 | 34.743566660013 | 8147 of 0 | <0a> |
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": 6671,
"vin": [ {
"gen": {
"height": 6611
}
}
],
"vout": [ {
"amount": 34743566660013,
"target": {
"tagged_key": {
"key": "1dd9692f1b5570916a25cf63695e20df8fd8cc21fb8649c4b356a3351a0d7748",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 69, 255, 174, 221, 215, 146, 54, 47, 117, 248, 9, 205, 14, 152, 182, 195, 216, 157, 60, 48, 42, 161, 46, 247, 229, 242, 220, 147, 83, 190, 158, 147, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}