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: 4fca3d06fb79ae04a1ae5d6471aa61c2590c942f84ee33943515ac5143c716ce
Tx prefix hash: b0d22225aef12bb115e3568372219eb2f7eb5c42767de37b8f95a1ff9763ef8f
Tx public key: ffdd204350e09ec3c462ad877b0ccf8620a7b3c116e56df8b7353e58ae809a84
| Timestamp: 1780684955 | Timestamp [UTC]: 2026-06-05 18:42:35 | Age [y:d:h:m:s]: 00:003:04:36:18 |
| Block: 5368 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2518 | RingCT/type: yes/0 |
| Extra: 01ffdd204350e09ec3c462ad877b0ccf8620a7b3c116e56df8b7353e58ae809a84020900000002e49593ff00 | ||
1 output(s) for total of 34.826035701550 HMNY
| stealth address | amount | amount idx | tag |
| 00: e195f2d48ce53c979b56936a1de4216747a7167e7409a3d2050f3cef31e50e6f | 34.826035701550 | 6803 of 0 | <75> |
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": 5428,
"vin": [ {
"gen": {
"height": 5368
}
}
],
"vout": [ {
"amount": 34826035701550,
"target": {
"tagged_key": {
"key": "e195f2d48ce53c979b56936a1de4216747a7167e7409a3d2050f3cef31e50e6f",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 255, 221, 32, 67, 80, 224, 158, 195, 196, 98, 173, 135, 123, 12, 207, 134, 32, 167, 179, 193, 22, 229, 109, 248, 183, 53, 62, 88, 174, 128, 154, 132, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}