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: 8bb4956fe0930587dd0780f2986c7a2eb48e1533a62fca1942409142c0983e38
Tx prefix hash: 9975276f2e199560447fee79204ecbe5de6b501f4326f09b8e302e7e136393b9
Tx public key: 53346a4674cb226a7f0fcff3f227036dc1420f90971bcd3fce60267ef1c6b32e
| Timestamp: 1780767446 | Timestamp [UTC]: 2026-06-06 17:37:26 | Age [y:d:h:m:s]: 00:002:07:58:31 |
| Block: 6629 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1257 | RingCT/type: yes/0 |
| Extra: 0153346a4674cb226a7f0fcff3f227036dc1420f90971bcd3fce60267ef1c6b32e020900000001e49593ff00 | ||
1 output(s) for total of 34.742373853653 HMNY
| stealth address | amount | amount idx | tag |
| 00: d233545180e45d365c879279a2a74fc11020b9b2cfb9ad219861d1b2358d3017 | 34.742373853653 | 8171 of 0 | <3e> |
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": 6689,
"vin": [ {
"gen": {
"height": 6629
}
}
],
"vout": [ {
"amount": 34742373853653,
"target": {
"tagged_key": {
"key": "d233545180e45d365c879279a2a74fc11020b9b2cfb9ad219861d1b2358d3017",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 83, 52, 106, 70, 116, 203, 34, 106, 127, 15, 207, 243, 242, 39, 3, 109, 193, 66, 15, 144, 151, 27, 205, 63, 206, 96, 38, 126, 241, 198, 179, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}