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: 4117ef67f488818379d4f049e250be12154e14ed719853c25da35795c8ff0765
Tx prefix hash: dcb156637e76d3bb6126a13995fe377ffe1505c7a63888f6b562fd764532abfb
Tx public key: 8ace7f0f5ce8de4f469b6fb04c4fc54208c0175b2fd414b7d7332db7b244e5cf
| Timestamp: 1780392068 | Timestamp [UTC]: 2026-06-02 09:21:08 | Age [y:d:h:m:s]: 00:006:16:14:49 |
| Block: 5216 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2670 | RingCT/type: yes/0 |
| Extra: 018ace7f0f5ce8de4f469b6fb04c4fc54208c0175b2fd414b7d7332db7b244e5cf02090000000126697be300 | ||
1 output(s) for total of 34.836133834441 HMNY
| stealth address | amount | amount idx | tag |
| 00: e492ba143dcbc3d37c3ffc368a1cf6eb6fe376559bd70482cabaa0c1aaf4facc | 34.836133834441 | 6601 of 0 | <8a> |
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": 5276,
"vin": [ {
"gen": {
"height": 5216
}
}
],
"vout": [ {
"amount": 34836133834441,
"target": {
"tagged_key": {
"key": "e492ba143dcbc3d37c3ffc368a1cf6eb6fe376559bd70482cabaa0c1aaf4facc",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 138, 206, 127, 15, 92, 232, 222, 79, 70, 155, 111, 176, 76, 79, 197, 66, 8, 192, 23, 91, 47, 212, 20, 183, 215, 51, 45, 183, 178, 68, 229, 207, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}