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: 5180b34d1e8fc7e2d20a5f62556bfc2c0076372248ddb822b4b3a231d8598a95
Tx prefix hash: a131be5816015f6a2c8cce738a3dfc81b3d12af691fddfa784bf3afac40e3872
Tx public key: 57ff0616c1e2c398d26f89b7327dce5c053d4c141376f283dd9af50cde031e2f
| Timestamp: 1779850288 | Timestamp [UTC]: 2026-05-27 02:51:28 | Age [y:d:h:m:s]: 00:012:20:27:25 |
| Block: 2518 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5368 | RingCT/type: yes/0 |
| Extra: 0157ff0616c1e2c398d26f89b7327dce5c053d4c141376f283dd9af50cde031e2f02090000000126697be300 | ||
1 output(s) for total of 35.015863728373 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7432b04b8dfdb084acf44fdb8794afc73f7c032dc512d8e3fbab39339746da73 | 35.015863728373 | 2964 of 0 | <15> |
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": 2578,
"vin": [ {
"gen": {
"height": 2518
}
}
],
"vout": [ {
"amount": 35015863728373,
"target": {
"tagged_key": {
"key": "7432b04b8dfdb084acf44fdb8794afc73f7c032dc512d8e3fbab39339746da73",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 87, 255, 6, 22, 193, 226, 195, 152, 210, 111, 137, 183, 50, 125, 206, 92, 5, 61, 76, 20, 19, 118, 242, 131, 221, 154, 245, 12, 222, 3, 30, 47, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}