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: de78bcaffd649d2d836826558126e4e9b089512f7dd9a23428399031cb0974ec
Tx prefix hash: 3bfc3f51afa283bfd4594326c68ad6daeb8532c7ced3988afd3d5859b5de83b3
Tx public key: dd326e78dca17f9b187abb26b4d5b9fdc93368ff40d44e07455b5736a20a47c0
| Timestamp: 1779853660 | Timestamp [UTC]: 2026-05-27 03:47:40 | Age [y:d:h:m:s]: 00:012:21:48:17 |
| Block: 2574 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5312 | RingCT/type: yes/0 |
| Extra: 01dd326e78dca17f9b187abb26b4d5b9fdc93368ff40d44e07455b5736a20a47c002090000000126697be300 | ||
1 output(s) for total of 35.012123826793 HMNY
| stealth address | amount | amount idx | tag |
| 00: b626d8829637729b45a6b93e9351f980f883fec1b8b12cc9e00f57000adf612f | 35.012123826793 | 3030 of 0 | <b2> |
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": 2634,
"vin": [ {
"gen": {
"height": 2574
}
}
],
"vout": [ {
"amount": 35012123826793,
"target": {
"tagged_key": {
"key": "b626d8829637729b45a6b93e9351f980f883fec1b8b12cc9e00f57000adf612f",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 221, 50, 110, 120, 220, 161, 127, 155, 24, 122, 187, 38, 180, 213, 185, 253, 201, 51, 104, 255, 64, 212, 78, 7, 69, 91, 87, 54, 162, 10, 71, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}