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: ec6d9f4bf1a9052f653a699d5af1f0125dc9d9ad416a82f7d4c84ee6cd106e9f
Tx prefix hash: 71e6f8f6f8e78ef95ba01c5e827a0d17728b987ed0e7b4a1723475976eb88a00
Tx public key: d4da8c788fcc548f2d6b174f0d9333081aab17a4c94821a224deeda21ef2b20f
| Timestamp: 1780868892 | Timestamp [UTC]: 2026-06-07 21:48:12 | Age [y:d:h:m:s]: 00:009:10:41:00 |
| Block: 7692 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1053 | RingCT/type: yes/0 |
| Extra: 01d4da8c788fcc548f2d6b174f0d9333081aab17a4c94821a224deeda21ef2b20f020900000001e49593ff00 | ||
1 output(s) for total of 34.672004582022 HMNY
| stealth address | amount | amount idx | tag |
| 00: 487a5827d10398a76a44b15d0e69d7756a7691b32dd3e32e29c2730cb7a01f38 | 34.672004582022 | 9514 of 0 | <a6> |
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": 7752,
"vin": [ {
"gen": {
"height": 7692
}
}
],
"vout": [ {
"amount": 34672004582022,
"target": {
"tagged_key": {
"key": "487a5827d10398a76a44b15d0e69d7756a7691b32dd3e32e29c2730cb7a01f38",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 212, 218, 140, 120, 143, 204, 84, 143, 45, 107, 23, 79, 13, 147, 51, 8, 26, 171, 23, 164, 201, 72, 33, 162, 36, 222, 237, 162, 30, 242, 178, 15, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}