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: deaab517ec8ae043c59ae2364ba54a5c704ced0ea70828720fce33447dd57584
Tx prefix hash: 60fd19820954633efd84470d9ae56efe4316d3641de5ad91b68759df7cb5a8ec
Tx public key: c30877f7b2d1a16207bf88238d590c6456f926f42c9f5996c3b2563dd8e5d8da
| Timestamp: 1779932855 | Timestamp [UTC]: 2026-05-28 01:47:35 | Age [y:d:h:m:s]: 00:016:09:14:41 |
| Block: 3413 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5332 | RingCT/type: yes/0 |
| Extra: 01c30877f7b2d1a16207bf88238d590c6456f926f42c9f5996c3b2563dd8e5d8da02090000000126697be300 | ||
1 output(s) for total of 34.956139885990 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18e4d4803f01825d2d0b91961eb33456fc24dbc32cb456675d69047ba8118c1c | 34.956139885990 | 4128 of 0 | <79> |
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": 3473,
"vin": [ {
"gen": {
"height": 3413
}
}
],
"vout": [ {
"amount": 34956139885990,
"target": {
"tagged_key": {
"key": "18e4d4803f01825d2d0b91961eb33456fc24dbc32cb456675d69047ba8118c1c",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 195, 8, 119, 247, 178, 209, 161, 98, 7, 191, 136, 35, 141, 89, 12, 100, 86, 249, 38, 244, 44, 159, 89, 150, 195, 178, 86, 61, 216, 229, 216, 218, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}