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: 953ecb822e765a06fbcb3069970e665267dfeeec7bc5b8cd0984e107d59ddebf
Tx prefix hash: 527e45164176b89c306148dd2c6bfcfb7c5364daa09db76100d9a52d713b2339
Tx public key: 42f5c0ec3de80a90d6693db0b58e0e6948c6b1f0b49170022342dcdcc3cefe7c
| Timestamp: 1780993230 | Timestamp [UTC]: 2026-06-09 08:20:30 | Age [y:d:h:m:s]: 00:000:08:31:26 |
| Block: 8273 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 449 | RingCT/type: yes/0 |
| Extra: 0142f5c0ec3de80a90d6693db0b58e0e6948c6b1f0b49170022342dcdcc3cefe7c020900000001e49593ff00 | ||
1 output(s) for total of 34.633603366947 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14a6d95cf1e01202fac35b68bd26007b6f8ce6dba5067d65afe5219eb35efd96 | 34.633603366947 | 10239 of 0 | <e1> |
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": 8333,
"vin": [ {
"gen": {
"height": 8273
}
}
],
"vout": [ {
"amount": 34633603366947,
"target": {
"tagged_key": {
"key": "14a6d95cf1e01202fac35b68bd26007b6f8ce6dba5067d65afe5219eb35efd96",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 66, 245, 192, 236, 61, 232, 10, 144, 214, 105, 61, 176, 181, 142, 14, 105, 72, 198, 177, 240, 180, 145, 112, 2, 35, 66, 220, 220, 195, 206, 254, 124, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}