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: 20893b36b377916dbe16b54c8caf03af1b2a07535c9ac530a159779962dd9b8b
Tx prefix hash: 90717b0f1d4713876592d4197971c534ad12f9b4974a910f1bd2a9648f4b0171
Tx public key: dc2ed5d14ac436e8ce7c956cb3d7012b621ccb023a7858b886f7a46f5aa2fdfd
| Timestamp: 1780687269 | Timestamp [UTC]: 2026-06-05 19:21:09 | Age [y:d:h:m:s]: 00:003:03:57:44 |
| Block: 5472 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2414 | RingCT/type: yes/0 |
| Extra: 01dc2ed5d14ac436e8ce7c956cb3d7012b621ccb023a7858b886f7a46f5aa2fdfd020900000001e49593ff00 | ||
1 output(s) for total of 34.819128139368 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64d5178b2792d85bcd6d9baf9297d0e40fae5187fd75c132aedefbc9fbcd8757 | 34.819128139368 | 6911 of 0 | <2c> |
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": 5532,
"vin": [ {
"gen": {
"height": 5472
}
}
],
"vout": [ {
"amount": 34819128139368,
"target": {
"tagged_key": {
"key": "64d5178b2792d85bcd6d9baf9297d0e40fae5187fd75c132aedefbc9fbcd8757",
"view_tag": "2c"
}
}
}
],
"extra": [ 1, 220, 46, 213, 209, 74, 196, 54, 232, 206, 124, 149, 108, 179, 215, 1, 43, 98, 28, 203, 2, 58, 120, 88, 184, 134, 247, 164, 111, 90, 162, 253, 253, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}