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: 7bc1b6b2f731fd2cbb0157e5d3c990279406494c7dd788925728906d2640f0e4
Tx prefix hash: 1cda8ba80c67a723b13e4924c6bdab820c3070711c8f38204598fa150889dd5b
Tx public key: 6428eab8cfb7c7d9845096e77dea178fb9897dd3d5693d85ade6f5a444b49342
| Timestamp: 1780015274 | Timestamp [UTC]: 2026-05-29 00:41:14 | Age [y:d:h:m:s]: 00:011:02:08:34 |
| Block: 4118 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3802 | RingCT/type: yes/0 |
| Extra: 016428eab8cfb7c7d9845096e77dea178fb9897dd3d5693d85ade6f5a444b4934202090000000226697be300 | ||
1 output(s) for total of 34.911783780659 HMNY
| stealth address | amount | amount idx | tag |
| 00: 22384e7b67a2d07fe5eb6ea50b8c21f903fc1566a21c050a4bbe821cf864b2f8 | 34.911783780659 | 5133 of 0 | <d3> |
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": 4178,
"vin": [ {
"gen": {
"height": 4118
}
}
],
"vout": [ {
"amount": 34911783780659,
"target": {
"tagged_key": {
"key": "22384e7b67a2d07fe5eb6ea50b8c21f903fc1566a21c050a4bbe821cf864b2f8",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 100, 40, 234, 184, 207, 183, 199, 217, 132, 80, 150, 231, 125, 234, 23, 143, 185, 137, 125, 211, 213, 105, 61, 133, 173, 230, 245, 164, 68, 180, 147, 66, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}