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: f1de2d52715ace7448be132febf4b0130d547ccf69e6650cf275f295934c30d9
Tx prefix hash: e8e33062206be87b7053c0de2a6cc0da2496908ce10d7a72637735bf964167d4
Tx public key: b54dc164b530b70f5ba9171878290e598433a4c871cbfb6c2104e17391c8363a
| Timestamp: 1780774499 | Timestamp [UTC]: 2026-06-06 19:34:59 | Age [y:d:h:m:s]: 00:002:06:00:58 |
| Block: 6701 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1185 | RingCT/type: yes/0 |
| Extra: 01b54dc164b530b70f5ba9171878290e598433a4c871cbfb6c2104e17391c8363a020900000001e49593ff00 | ||
1 output(s) for total of 34.737603037709 HMNY
| stealth address | amount | amount idx | tag |
| 00: 529b66d3112f9fb889e8799ccb2add1f7841488fa9fd7a218a6a5d2292b22cb9 | 34.737603037709 | 8265 of 0 | <fe> |
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": 6761,
"vin": [ {
"gen": {
"height": 6701
}
}
],
"vout": [ {
"amount": 34737603037709,
"target": {
"tagged_key": {
"key": "529b66d3112f9fb889e8799ccb2add1f7841488fa9fd7a218a6a5d2292b22cb9",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 181, 77, 193, 100, 181, 48, 183, 15, 91, 169, 23, 24, 120, 41, 14, 89, 132, 51, 164, 200, 113, 203, 251, 108, 33, 4, 225, 115, 145, 200, 54, 58, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}