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: db18312d2690141b07566a53ffb3c9f483f285a3ecc35990b70bbcee0954613f
Tx prefix hash: 2efdbffde447dd9bec2e15a1f6af2efb4eb7e9b1069f6ebfcd9b10e0cd6065bd
Tx public key: 30cd3d6f0a932195ce1b5874c11d95f990a691892611adca81be0e88ef5e9260
| Timestamp: 1780989002 | Timestamp [UTC]: 2026-06-09 07:10:02 | Age [y:d:h:m:s]: 00:000:08:49:42 |
| Block: 8191 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 500 | RingCT/type: yes/0 |
| Extra: 0130cd3d6f0a932195ce1b5874c11d95f990a691892611adca81be0e88ef5e9260020900000001e49593ff00 | ||
1 output(s) for total of 34.647245380930 HMNY
| stealth address | amount | amount idx | tag |
| 00: 477f3052df36f30e60f920ce8fe9d5d54de8d0323893710d51e62a6334c876ce | 34.647245380930 | 10141 of 0 | <af> |
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": 8251,
"vin": [ {
"gen": {
"height": 8191
}
}
],
"vout": [ {
"amount": 34647245380930,
"target": {
"tagged_key": {
"key": "477f3052df36f30e60f920ce8fe9d5d54de8d0323893710d51e62a6334c876ce",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 48, 205, 61, 111, 10, 147, 33, 149, 206, 27, 88, 116, 193, 29, 149, 249, 144, 166, 145, 137, 38, 17, 173, 202, 129, 190, 14, 136, 239, 94, 146, 96, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}