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: 943f1cd77736d49de1407949826302d50de6ffcd6423ee20fd016552716b1530
Tx prefix hash: df1b14d7f46b273721a7d60821e8503acab7f467d04c96d5d41baa806b9d50a8
Tx public key: 6438d417a81a1870a864eb77f9be2b2051ca80edf85841fcf0b5e239fe6fa923
| Timestamp: 1781001114 | Timestamp [UTC]: 2026-06-09 10:31:54 | Age [y:d:h:m:s]: 00:006:00:42:06 |
| Block: 8453 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 292 | RingCT/type: yes/0 |
| Extra: 016438d417a81a1870a864eb77f9be2b2051ca80edf85841fcf0b5e239fe6fa923020900000002e49593ff00 | ||
1 output(s) for total of 34.621714892432 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b125d89ab4117b9167a60b1bd9a00831bdd3b85197ae8677bb5111fc297bec4 | 34.621714892432 | 10445 of 0 | <df> |
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": 8513,
"vin": [ {
"gen": {
"height": 8453
}
}
],
"vout": [ {
"amount": 34621714892432,
"target": {
"tagged_key": {
"key": "1b125d89ab4117b9167a60b1bd9a00831bdd3b85197ae8677bb5111fc297bec4",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 100, 56, 212, 23, 168, 26, 24, 112, 168, 100, 235, 119, 249, 190, 43, 32, 81, 202, 128, 237, 248, 88, 65, 252, 240, 181, 226, 57, 254, 111, 169, 35, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}