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: f6b1c93f6c61fc97c50c3ae560341ea1d0a8403a1dbec9c4ba776dc434e3849f
Tx prefix hash: 3eb396317e15580b436dff77e6761529cedc8080f30900a6578a5341ab376fd9
Tx public key: d0bc3757ddb3c613b2a28209ea15d13d4ea0b396fe81735937ad1073835cd2e8
| Timestamp: 1780049048 | Timestamp [UTC]: 2026-05-29 10:04:08 | Age [y:d:h:m:s]: 00:010:15:31:49 |
| Block: 4374 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3512 | RingCT/type: yes/0 |
| Extra: 01d0bc3757ddb3c613b2a28209ea15d13d4ea0b396fe81735937ad1073835cd2e802090000000326697be300 | ||
1 output(s) for total of 34.892125233736 HMNY
| stealth address | amount | amount idx | tag |
| 00: e90c47b1951ac1087f5a978035f24c23a6f01c02e46c6670317bbc2fb284e7fd | 34.892125233736 | 5471 of 0 | <d6> |
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": 4434,
"vin": [ {
"gen": {
"height": 4374
}
}
],
"vout": [ {
"amount": 34892125233736,
"target": {
"tagged_key": {
"key": "e90c47b1951ac1087f5a978035f24c23a6f01c02e46c6670317bbc2fb284e7fd",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 208, 188, 55, 87, 221, 179, 198, 19, 178, 162, 130, 9, 234, 21, 209, 61, 78, 160, 179, 150, 254, 129, 115, 89, 55, 173, 16, 115, 131, 92, 210, 232, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}