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: 4f69af8487bef84e394e1d6498540d82d23ddf489ea8029e19be6cc7bb45e62b
Tx prefix hash: 47aadaa012f73e8c7542eba1970b612abca1a2b38cb48d7ae9c4b60aaea5e60c
Tx public key: 75cf6c502e8bc5a087c2a4fd178fe48ec7d276019964a18ea69e6a87b2500b77
| Timestamp: 1780992465 | Timestamp [UTC]: 2026-06-09 08:07:45 | Age [y:d:h:m:s]: 00:000:10:14:07 |
| Block: 8261 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 484 | RingCT/type: yes/0 |
| Extra: 0175cf6c502e8bc5a087c2a4fd178fe48ec7d276019964a18ea69e6a87b2500b77020900000002e49593ff00 | ||
1 output(s) for total of 34.634396077047 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a86e9865694c597aaf0e622164f9b4c2c2090f8345a7fe5c4aed9c4dae1b14b | 34.634396077047 | 10223 of 0 | <1c> |
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": 8321,
"vin": [ {
"gen": {
"height": 8261
}
}
],
"vout": [ {
"amount": 34634396077047,
"target": {
"tagged_key": {
"key": "5a86e9865694c597aaf0e622164f9b4c2c2090f8345a7fe5c4aed9c4dae1b14b",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 117, 207, 108, 80, 46, 139, 197, 160, 135, 194, 164, 253, 23, 143, 228, 142, 199, 210, 118, 1, 153, 100, 161, 142, 166, 158, 106, 135, 178, 80, 11, 119, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}