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: 8a61ba4e8536c5f24aba74a9621735ba3cc70ba5f12516b588a85fc0c74100b7
Tx prefix hash: 2806228be17e3bbae6aec96e4d2c37a3b0153bde8e0704f1e78066a612ee797e
Tx public key: 7c7d35e7dd64525907da86339968c3a0f7b77e3506d78a62fe5a29e050528929
| Timestamp: 1780056095 | Timestamp [UTC]: 2026-05-29 12:01:35 | Age [y:d:h:m:s]: 00:010:13:34:22 |
| Block: 4458 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3428 | RingCT/type: yes/0 |
| Extra: 017c7d35e7dd64525907da86339968c3a0f7b77e3506d78a62fe5a29e05052892902090000000626697be300 | ||
1 output(s) for total of 34.886535354637 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25a07940b6579b1dc60be52d52428e56656acd1d4354738d17531ad43ed083a1 | 34.886535354637 | 5581 of 0 | <35> |
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": 4518,
"vin": [ {
"gen": {
"height": 4458
}
}
],
"vout": [ {
"amount": 34886535354637,
"target": {
"tagged_key": {
"key": "25a07940b6579b1dc60be52d52428e56656acd1d4354738d17531ad43ed083a1",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 124, 125, 53, 231, 221, 100, 82, 89, 7, 218, 134, 51, 153, 104, 195, 160, 247, 183, 126, 53, 6, 215, 138, 98, 254, 90, 41, 224, 80, 82, 137, 41, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}