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: 59db8a57e054d528e4a0899812734c7581d9e810fdf96669e264b4c3b4a8e0a3
Tx prefix hash: 335c957af1b8a8a88ed9731062f62f5eec31b5fd608dfd9ee3a5affddc01fcdd
Tx public key: 6398e9b57c17105a2132c807090d714a646ebdfa5c48b883aefddcbea3b120ab
| Timestamp: 1780995511 | Timestamp [UTC]: 2026-06-09 08:58:31 | Age [y:d:h:m:s]: 00:000:03:39:14 |
| Block: 8321 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 253 | RingCT/type: yes/0 |
| Extra: 016398e9b57c17105a2132c807090d714a646ebdfa5c48b883aefddcbea3b120ab020900000001e49593ff00 | ||
1 output(s) for total of 34.630432707977 HMNY
| stealth address | amount | amount idx | tag |
| 00: 713c9aa9e4c779bf9a2b87c21bcc04b383cf9ac436465340eeb7f63e749b46f7 | 34.630432707977 | 10293 of 0 | <51> |
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": 8381,
"vin": [ {
"gen": {
"height": 8321
}
}
],
"vout": [ {
"amount": 34630432707977,
"target": {
"tagged_key": {
"key": "713c9aa9e4c779bf9a2b87c21bcc04b383cf9ac436465340eeb7f63e749b46f7",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 99, 152, 233, 181, 124, 23, 16, 90, 33, 50, 200, 7, 9, 13, 113, 74, 100, 110, 189, 250, 92, 72, 184, 131, 174, 253, 220, 190, 163, 177, 32, 171, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}