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: 353ceded7f68b5758542ca5aea2cc4c33d5baa2e3f4da4d3f4a36420216493d3
Tx prefix hash: 50136d511fe5911313904eb45262057ac0a91161d28a267ef97bb76e102e0896
Tx public key: 5918fbda6e98510db99ae42547e62d04745eacf0fe8fa3386f1a4d462311d024
| Timestamp: 1780979396 | Timestamp [UTC]: 2026-06-09 04:29:56 | Age [y:d:h:m:s]: 00:000:04:30:03 |
| Block: 8002 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 327 | RingCT/type: yes/0 |
| Extra: 015918fbda6e98510db99ae42547e62d04745eacf0fe8fa3386f1a4d462311d024020900000002e49593ff00 | ||
1 output(s) for total of 34.651509825958 HMNY
| stealth address | amount | amount idx | tag |
| 00: bef8eb92ce90eb2b2820e114e27146fa72abffe3a10de8e0757204c836d0a3db | 34.651509825958 | 9922 of 0 | <4c> |
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": 8062,
"vin": [ {
"gen": {
"height": 8002
}
}
],
"vout": [ {
"amount": 34651509825958,
"target": {
"tagged_key": {
"key": "bef8eb92ce90eb2b2820e114e27146fa72abffe3a10de8e0757204c836d0a3db",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 89, 24, 251, 218, 110, 152, 81, 13, 185, 154, 228, 37, 71, 230, 45, 4, 116, 94, 172, 240, 254, 143, 163, 56, 111, 26, 77, 70, 35, 17, 208, 36, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}