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: 556bbfffea9539bc0cec9608401c9858728387679738d63aad2545b3398531c7
Tx prefix hash: 5b1a634f892810b7dabf38d79a3d336de94b2db0091c07a362d07f15c217cd72
Tx public key: 8bde3efb8f639e9e07f44e91a8f229d9423f84215cacdb774a9cb89ff438ca3d
| Timestamp: 1780994694 | Timestamp [UTC]: 2026-06-09 08:44:54 | Age [y:d:h:m:s]: 00:004:02:17:22 |
| Block: 8305 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 440 | RingCT/type: yes/0 |
| Extra: 018bde3efb8f639e9e07f44e91a8f229d9423f84215cacdb774a9cb89ff438ca3d020900000001e49593ff00 | ||
1 output(s) for total of 34.631489562047 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f59f1dfa4cfabc75b7bd277a1ad7f773270518c9d00feb77086f16a23c08921 | 34.631489562047 | 10275 of 0 | <28> |
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": 8365,
"vin": [ {
"gen": {
"height": 8305
}
}
],
"vout": [ {
"amount": 34631489562047,
"target": {
"tagged_key": {
"key": "6f59f1dfa4cfabc75b7bd277a1ad7f773270518c9d00feb77086f16a23c08921",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 139, 222, 62, 251, 143, 99, 158, 158, 7, 244, 78, 145, 168, 242, 41, 217, 66, 63, 132, 33, 92, 172, 219, 119, 74, 156, 184, 159, 244, 56, 202, 61, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}