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: 825d3a39c9e7526f6f3e5574ed0dac81541b16dcc98bb8fc1c4f840069f332d4
Tx prefix hash: 2f49c048de9afe3acb3fcd8ab57a86aeb11a21c677e001ddd2a4c7f6617c59a8
Tx public key: 304f2c076c23435038915dd0eba3c3e0e4fbdc885bd113eb44c4b3867b6050d8
| Timestamp: 1780751956 | Timestamp [UTC]: 2026-06-06 13:19:16 | Age [y:d:h:m:s]: 00:002:12:16:41 |
| Block: 6497 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1389 | RingCT/type: yes/0 |
| Extra: 01304f2c076c23435038915dd0eba3c3e0e4fbdc885bd113eb44c4b3867b6050d8020900000006e49593ff00 | ||
1 output(s) for total of 34.751122051360 HMNY
| stealth address | amount | amount idx | tag |
| 00: 27023f9b0e91825f6591148f53401520a3390c2a2fdab5813dba3d82ff336bf8 | 34.751122051360 | 7994 of 0 | <e2> |
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": 6557,
"vin": [ {
"gen": {
"height": 6497
}
}
],
"vout": [ {
"amount": 34751122051360,
"target": {
"tagged_key": {
"key": "27023f9b0e91825f6591148f53401520a3390c2a2fdab5813dba3d82ff336bf8",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 48, 79, 44, 7, 108, 35, 67, 80, 56, 145, 93, 208, 235, 163, 195, 224, 228, 251, 220, 136, 91, 209, 19, 235, 68, 196, 179, 134, 123, 96, 80, 216, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}