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: ff3db2c79cd8718bba85c721fcdb68d85531d3bdbe2c8dd0de7cda4b82515024
Tx prefix hash: 52a998a9fddf3bae3909e421ce3fc7e4ecfe49bd973898bfe4f69d08646f6158
Tx public key: 1ca78cb3dd593a37e64b2d1beaf8c9746c4f31d9ff14f221af1316a420ae6f4c
| Timestamp: 1780693314 | Timestamp [UTC]: 2026-06-05 21:01:54 | Age [y:d:h:m:s]: 00:007:14:00:22 |
| Block: 5862 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2883 | RingCT/type: yes/0 |
| Extra: 011ca78cb3dd593a37e64b2d1beaf8c9746c4f31d9ff14f221af1316a420ae6f4c020900000001e49593ff00 | ||
1 output(s) for total of 34.793236981229 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74c453aa334ac5f2f7e203d32ba79cff109d4090418317ea2d366ae4fa2eb929 | 34.793236981229 | 7321 of 0 | <8e> |
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": 5922,
"vin": [ {
"gen": {
"height": 5862
}
}
],
"vout": [ {
"amount": 34793236981229,
"target": {
"tagged_key": {
"key": "74c453aa334ac5f2f7e203d32ba79cff109d4090418317ea2d366ae4fa2eb929",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 28, 167, 140, 179, 221, 89, 58, 55, 230, 75, 45, 27, 234, 248, 201, 116, 108, 79, 49, 217, 255, 20, 242, 33, 175, 19, 22, 164, 32, 174, 111, 76, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}