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: f406e9bb0024b1db3941e03d262ecd8b8921321717255b291d049418be504197
Tx prefix hash: 54e73be3018d15dd0026c8fcacac9b4f212bb61eb20774ea523056db7d7ba111
Tx public key: 11569b36ae87ee9904daad8aa92394be5f84e1baf3274d2b874086e5b6851bc7
| Timestamp: 1780989521 | Timestamp [UTC]: 2026-06-09 07:18:41 | Age [y:d:h:m:s]: 00:000:07:30:14 |
| Block: 8197 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 460 | RingCT/type: yes/0 |
| Extra: 0111569b36ae87ee9904daad8aa92394be5f84e1baf3274d2b874086e5b6851bc7020900000001e49593ff00 | ||
1 output(s) for total of 34.638624170689 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5dc5aef19848a7bdea2c99fd27e3d74de48de5849f9392207bcb6760f13abcef | 34.638624170689 | 10149 of 0 | <de> |
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": 8257,
"vin": [ {
"gen": {
"height": 8197
}
}
],
"vout": [ {
"amount": 34638624170689,
"target": {
"tagged_key": {
"key": "5dc5aef19848a7bdea2c99fd27e3d74de48de5849f9392207bcb6760f13abcef",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 17, 86, 155, 54, 174, 135, 238, 153, 4, 218, 173, 138, 169, 35, 148, 190, 95, 132, 225, 186, 243, 39, 77, 43, 135, 64, 134, 229, 182, 133, 27, 199, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}