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: 727c373176027045e5e37346a219c5d6c009de4104352454b09ee27f75052f0d
Tx prefix hash: 28ecd9145dab6215e77d78f2301373b23d9e8864fc92ba9fb406355e4371510d
Tx public key: 9f588c0fc1dbea72b06ee02792fd9e7ac37100bc7966c26405753e87d64c1c23
| Timestamp: 1779640587 | Timestamp [UTC]: 2026-05-24 16:36:27 | Age [y:d:h:m:s]: 00:015:06:42:26 |
| Block: 1303 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6583 | RingCT/type: yes/0 |
| Extra: 019f588c0fc1dbea72b06ee02792fd9e7ac37100bc7966c26405753e87d64c1c23020900000001ba6d17be00 | ||
1 output(s) for total of 35.097104668198 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6d7c3abbbb6a0cf66da9e09df2f99826855909ad130cebecaae720f7fae9a81 | 35.097104668198 | 1451 of 0 | <37> |
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": 1363,
"vin": [ {
"gen": {
"height": 1303
}
}
],
"vout": [ {
"amount": 35097104668198,
"target": {
"tagged_key": {
"key": "b6d7c3abbbb6a0cf66da9e09df2f99826855909ad130cebecaae720f7fae9a81",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 159, 88, 140, 15, 193, 219, 234, 114, 176, 110, 224, 39, 146, 253, 158, 122, 195, 113, 0, 188, 121, 102, 194, 100, 5, 117, 62, 135, 214, 76, 28, 35, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}