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: a0ecf840fc7a04f7412610665801604a543424a6881ca9190df84ffc8cdb86b1
Tx prefix hash: dc71165f1cf305aed410f170340bbcc6f71d0d4bcf7c9f30e247a82915fd03d0
Tx public key: 6b7d728f7775261ce6c2221ef975c7f9ed75e7a9df8833c579c4755ff0a070fb
| Timestamp: 1780704524 | Timestamp [UTC]: 2026-06-06 00:08:44 | Age [y:d:h:m:s]: 00:003:01:27:13 |
| Block: 6093 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1793 | RingCT/type: yes/0 |
| Extra: 016b7d728f7775261ce6c2221ef975c7f9ed75e7a9df8833c579c4755ff0a070fb020900000001e49593ff00 | ||
1 output(s) for total of 34.777910528839 HMNY
| stealth address | amount | amount idx | tag |
| 00: 26b49713c12d8be4abb429184cd71ac566cb7c9a6be770fec8cf3cd55e744901 | 34.777910528839 | 7564 of 0 | <40> |
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": 6153,
"vin": [ {
"gen": {
"height": 6093
}
}
],
"vout": [ {
"amount": 34777910528839,
"target": {
"tagged_key": {
"key": "26b49713c12d8be4abb429184cd71ac566cb7c9a6be770fec8cf3cd55e744901",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 107, 125, 114, 143, 119, 117, 38, 28, 230, 194, 34, 30, 249, 117, 199, 249, 237, 117, 231, 169, 223, 136, 51, 197, 121, 196, 117, 95, 240, 160, 112, 251, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}