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: 96e60a0ec7ae5a8b675c48cba718f20f18581064104fc1c8f1224647f14ced72
Tx prefix hash: bd1a92c0874588352ea2ee53693d3c5caef956c7e6a65ae96e6e4990ae01f4e8
Tx public key: 413ebb607b2950825578ab8ddd8710a247e27d5decea116d9dde56b7e1f282cc
| Timestamp: 1780744657 | Timestamp [UTC]: 2026-06-06 11:17:37 | Age [y:d:h:m:s]: 00:002:14:18:20 |
| Block: 6447 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1439 | RingCT/type: yes/0 |
| Extra: 01413ebb607b2950825578ab8ddd8710a247e27d5decea116d9dde56b7e1f282cc020900000002e49593ff00 | ||
1 output(s) for total of 34.754436337813 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe8628c5ee40f72e88b7d3026bc9b94542898737d592d2f79f51dd363e27b019 | 34.754436337813 | 7940 of 0 | <b0> |
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": 6507,
"vin": [ {
"gen": {
"height": 6447
}
}
],
"vout": [ {
"amount": 34754436337813,
"target": {
"tagged_key": {
"key": "fe8628c5ee40f72e88b7d3026bc9b94542898737d592d2f79f51dd363e27b019",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 65, 62, 187, 96, 123, 41, 80, 130, 85, 120, 171, 141, 221, 135, 16, 162, 71, 226, 125, 93, 236, 234, 17, 109, 157, 222, 86, 183, 225, 242, 130, 204, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}