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: 76e7055cb8e7f13f1ee45231c0fada8be32595bfe19766920285a26cf7873630
Tx prefix hash: 08a5218a28e5fef0c5b3d0761c4a0d159699f6b536cffecd2502dacfe17a47e8
Tx public key: 067ad5b3309c73e80678971afa996c4c5ea558c35b9981ce80af090c7cebfb6a
| Timestamp: 1780048944 | Timestamp [UTC]: 2026-05-29 10:02:24 | Age [y:d:h:m:s]: 00:010:15:33:33 |
| Block: 4371 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3515 | RingCT/type: yes/0 |
| Extra: 01067ad5b3309c73e80678971afa996c4c5ea558c35b9981ce80af090c7cebfb6a02090000000226697be300 | ||
1 output(s) for total of 34.892324888840 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd246afb851b0ea62f6ef34fdd529df6797eead7f792eb29bd1306f806df9627 | 34.892324888840 | 5468 of 0 | <6e> |
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": 4431,
"vin": [ {
"gen": {
"height": 4371
}
}
],
"vout": [ {
"amount": 34892324888840,
"target": {
"tagged_key": {
"key": "fd246afb851b0ea62f6ef34fdd529df6797eead7f792eb29bd1306f806df9627",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 6, 122, 213, 179, 48, 156, 115, 232, 6, 120, 151, 26, 250, 153, 108, 76, 94, 165, 88, 195, 91, 153, 129, 206, 128, 175, 9, 12, 124, 235, 251, 106, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}