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: 6f4cd6a617b3ea394641475f5b9f807ea137c919356a8e4c1bc3d17499bbe27e
Tx prefix hash: a0e04f872b1db1dc5c76c2f08a88cdb315f0dd85689eae41a33af8034f0dd126
Tx public key: d3d00d8a36420e755f1c9740d6178c4bd741e1686cdb114add85c431dc8c8654
| Timestamp: 1780776329 | Timestamp [UTC]: 2026-06-06 20:05:29 | Age [y:d:h:m:s]: 00:002:05:30:28 |
| Block: 6721 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1165 | RingCT/type: yes/0 |
| Extra: 01d3d00d8a36420e755f1c9740d6178c4bd741e1686cdb114add85c431dc8c8654020900000001e49593ff00 | ||
1 output(s) for total of 34.736277927327 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43886781261f54d2f3decde03fcc798d8c44c5c834a04f08da4a3006a0ea8702 | 34.736277927327 | 8291 of 0 | <db> |
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": 6781,
"vin": [ {
"gen": {
"height": 6721
}
}
],
"vout": [ {
"amount": 34736277927327,
"target": {
"tagged_key": {
"key": "43886781261f54d2f3decde03fcc798d8c44c5c834a04f08da4a3006a0ea8702",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 211, 208, 13, 138, 54, 66, 14, 117, 95, 28, 151, 64, 214, 23, 140, 75, 215, 65, 225, 104, 108, 219, 17, 74, 221, 133, 196, 49, 220, 140, 134, 84, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}