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: 8ece86ead14eaf0f9e5d266aef3141b8d491d2b63f7d39f4327ba2ab1d23a8b7
Tx prefix hash: 109cb6e91358845695575e779057ed45da8373b9e4a39a17d40b1b59d94fcd5d
Tx public key: ca2dbb6f0e5d457896bb1e92ea65f06c18a377bd34f87b31e8a2c6ed5dbe60e9
| Timestamp: 1779638779 | Timestamp [UTC]: 2026-05-24 16:06:19 | Age [y:d:h:m:s]: 00:015:08:40:28 |
| Block: 1218 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6668 | RingCT/type: yes/0 |
| Extra: 01ca2dbb6f0e5d457896bb1e92ea65f06c18a377bd34f87b31e8a2c6ed5dbe60e9020900000001ba6d17be00 | ||
1 output(s) for total of 35.102795240145 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a3b7ed1f4d8fcdf5ad629f111bed9972057ad6448940a75f0e55df511104a5d | 35.102795240145 | 1362 of 0 | <0f> |
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": 1278,
"vin": [ {
"gen": {
"height": 1218
}
}
],
"vout": [ {
"amount": 35102795240145,
"target": {
"tagged_key": {
"key": "5a3b7ed1f4d8fcdf5ad629f111bed9972057ad6448940a75f0e55df511104a5d",
"view_tag": "0f"
}
}
}
],
"extra": [ 1, 202, 45, 187, 111, 14, 93, 69, 120, 150, 187, 30, 146, 234, 101, 240, 108, 24, 163, 119, 189, 52, 248, 123, 49, 232, 162, 198, 237, 93, 190, 96, 233, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}