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: 30bb8c27afe5db8134c825d726e39db4d7de04c418c14808d0adc759c255ca18
Tx prefix hash: e6018e8a448522d244049c147b5d0baae1b04027df39033d423a9464e25551b0
Tx public key: 9a054f20a57a2b84b068a8ad7c71c5d3e9e35dc179e2f7dc89ec18c843be7fea
| Timestamp: 1780080482 | Timestamp [UTC]: 2026-05-29 18:48:02 | Age [y:d:h:m:s]: 00:010:06:47:55 |
| Block: 4760 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3126 | RingCT/type: yes/0 |
| Extra: 019a054f20a57a2b84b068a8ad7c71c5d3e9e35dc179e2f7dc89ec18c843be7fea02090000000426697be300 | ||
1 output(s) for total of 34.866445804793 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10d7454e01cb47ca3f5bae6e0a8474290a01ef70fb283308fcc4428a7cbb211b | 34.866445804793 | 5981 of 0 | <11> |
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": 4820,
"vin": [ {
"gen": {
"height": 4760
}
}
],
"vout": [ {
"amount": 34866445804793,
"target": {
"tagged_key": {
"key": "10d7454e01cb47ca3f5bae6e0a8474290a01ef70fb283308fcc4428a7cbb211b",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 154, 5, 79, 32, 165, 122, 43, 132, 176, 104, 168, 173, 124, 113, 197, 211, 233, 227, 93, 193, 121, 226, 247, 220, 137, 236, 24, 200, 67, 190, 127, 234, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}