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: 2af1ed580a4b29fd571aeb70d8684a0e2bd4c43c37845781cf90dce975fd9244
Tx prefix hash: b81bc7059e63f8e192b54b9fb6098c3f311746543ab41ad3c4fe8dc2ef105d9d
Tx public key: 31b8f93c7ec98b35e632bc8b7920b4830779e1b6c0ae9d77078806ba2f1cfe39
| Timestamp: 1780323148 | Timestamp [UTC]: 2026-06-01 14:12:28 | Age [y:d:h:m:s]: 00:007:11:23:29 |
| Block: 5065 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2821 | RingCT/type: yes/0 |
| Extra: 0131b8f93c7ec98b35e632bc8b7920b4830779e1b6c0ae9d77078806ba2f1cfe3902090000003f26697be300 | ||
1 output(s) for total of 34.846168431460 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5482e6f8616ad614c1689235d2aeeb3b5dfe5452b79f9de1afcc2b31ad335678 | 34.846168431460 | 6440 of 0 | <e6> |
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": 5125,
"vin": [ {
"gen": {
"height": 5065
}
}
],
"vout": [ {
"amount": 34846168431460,
"target": {
"tagged_key": {
"key": "5482e6f8616ad614c1689235d2aeeb3b5dfe5452b79f9de1afcc2b31ad335678",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 49, 184, 249, 60, 126, 201, 139, 53, 230, 50, 188, 139, 121, 32, 180, 131, 7, 121, 225, 182, 192, 174, 157, 119, 7, 136, 6, 186, 47, 28, 254, 57, 2, 9, 0, 0, 0, 63, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}