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: 4394fb8d5fbec20175eb59954034782d6a66c4f31a7574b09cb9784a7e061925
Tx prefix hash: 741e3eb411df29566ff44bd8442dc75b19fd7dc06403527097df4950e7fe4f5d
Tx public key: b76e0255cec666ffae1cc768ffd62bc51e651deaecc6c1a0b815425b01d49ca2
| Timestamp: 1780749734 | Timestamp [UTC]: 2026-06-06 12:42:14 | Age [y:d:h:m:s]: 00:006:22:20:02 |
| Block: 6481 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2264 | RingCT/type: yes/0 |
| Extra: 01b76e0255cec666ffae1cc768ffd62bc51e651deaecc6c1a0b815425b01d49ca2020900000003e49593ff00 | ||
1 output(s) for total of 34.752182588636 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32a4c02257506c3e9187e3ef84513c139872d65dcce0f761fab0111ca8069780 | 34.752182588636 | 7976 of 0 | <81> |
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": 6541,
"vin": [ {
"gen": {
"height": 6481
}
}
],
"vout": [ {
"amount": 34752182588636,
"target": {
"tagged_key": {
"key": "32a4c02257506c3e9187e3ef84513c139872d65dcce0f761fab0111ca8069780",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 183, 110, 2, 85, 206, 198, 102, 255, 174, 28, 199, 104, 255, 214, 43, 197, 30, 101, 29, 234, 236, 198, 193, 160, 184, 21, 66, 91, 1, 212, 156, 162, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}