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: 1434e2288a77fcd077b51eccf47063406f57524eb0d8bd0c25b65392e82d6054
Tx prefix hash: c93e6662852acd47958721b3b2084f086b71da7a9dd9bbb528e700d5efefa88d
Tx public key: 0e107dc191e8e98a2e265593fe3d23021ecfdc237dce376ff60e2a91affcc553
| Timestamp: 1780985987 | Timestamp [UTC]: 2026-06-09 06:19:47 | Age [y:d:h:m:s]: 00:000:08:29:08 |
| Block: 8141 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 501 | RingCT/type: yes/0 |
| Extra: 010e107dc191e8e98a2e265593fe3d23021ecfdc237dce376ff60e2a91affcc553020900000002e49593ff00 | ||
1 output(s) for total of 34.648156176033 HMNY
| stealth address | amount | amount idx | tag |
| 00: cbff99a6077524528d062e09d0f83f3e05ee61b1657791f89cdc6a82834579e6 | 34.648156176033 | 10081 of 0 | <d8> |
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": 8201,
"vin": [ {
"gen": {
"height": 8141
}
}
],
"vout": [ {
"amount": 34648156176033,
"target": {
"tagged_key": {
"key": "cbff99a6077524528d062e09d0f83f3e05ee61b1657791f89cdc6a82834579e6",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 14, 16, 125, 193, 145, 232, 233, 138, 46, 38, 85, 147, 254, 61, 35, 2, 30, 207, 220, 35, 125, 206, 55, 111, 246, 14, 42, 145, 175, 252, 197, 83, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}