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: 1914c90cfb27e13dc5353ec1fd83628f5d92e0392d68a973eda62dfb5e2e7bae
Tx prefix hash: 740327513d9a7f514517d9a7964c17956fc3218a250499e2fe6ee7271fb2e06b
Tx public key: 11102ab1a01ea5ae33f84fc315d8d28ae36d81c2fca7913b4f63549ee767b7c4
| Timestamp: 1780704532 | Timestamp [UTC]: 2026-06-06 00:08:52 | Age [y:d:h:m:s]: 00:003:03:29:58 |
| Block: 6095 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1849 | RingCT/type: yes/0 |
| Extra: 0111102ab1a01ea5ae33f84fc315d8d28ae36d81c2fca7913b4f63549ee767b7c4020900000001e49593ff00 | ||
1 output(s) for total of 34.777777861765 HMNY
| stealth address | amount | amount idx | tag |
| 00: a94563747c8e2e42b96df5b9ffbcc8144658f1bff0c995236b757a507b2dd216 | 34.777777861765 | 7566 of 0 | <34> |
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": 6155,
"vin": [ {
"gen": {
"height": 6095
}
}
],
"vout": [ {
"amount": 34777777861765,
"target": {
"tagged_key": {
"key": "a94563747c8e2e42b96df5b9ffbcc8144658f1bff0c995236b757a507b2dd216",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 17, 16, 42, 177, 160, 30, 165, 174, 51, 248, 79, 195, 21, 216, 210, 138, 227, 109, 129, 194, 252, 167, 145, 59, 79, 99, 84, 158, 231, 103, 183, 196, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}