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: 3419cc9023e1e0bb291e09e666d6d3e238694701e6b74af5df7ff894587c9ad8
Tx prefix hash: 6ef46dcab2708020e5324ce402358695213c2187b7992cc7d2338ecbd8016355
Tx public key: c9a3fc0e8991b439c10b4387e34afe9d593495718ab2e49e2dc3d622e5899d0d
| Timestamp: 1780738373 | Timestamp [UTC]: 2026-06-06 09:32:53 | Age [y:d:h:m:s]: 00:002:16:03:04 |
| Block: 6387 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1499 | RingCT/type: yes/0 |
| Extra: 01c9a3fc0e8991b439c10b4387e34afe9d593495718ab2e49e2dc3d622e5899d0d020900000002e49593ff00 | ||
1 output(s) for total of 34.758413898797 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6733bd7e61e47c704575744e4d826392d481ea8ea6910910d84452468d13b9fd | 34.758413898797 | 7876 of 0 | <13> |
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": 6447,
"vin": [ {
"gen": {
"height": 6387
}
}
],
"vout": [ {
"amount": 34758413898797,
"target": {
"tagged_key": {
"key": "6733bd7e61e47c704575744e4d826392d481ea8ea6910910d84452468d13b9fd",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 201, 163, 252, 14, 137, 145, 180, 57, 193, 11, 67, 135, 227, 74, 254, 157, 89, 52, 149, 113, 138, 178, 228, 158, 45, 195, 214, 34, 229, 137, 157, 13, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}