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: c89a38ebec9b8632dd6867d2b1a758da7cea19e9d2558070d7957280943748f1
Tx prefix hash: 35678f54d0b3f9604ca05b692bb2e1dcc642de858bbd885ca93faadfc14cedd2
Tx public key: 66b951167ca0a0f30633278906c9358391276c7a457c1196d320d2e30dc62cb1
| Timestamp: 1781014498 | Timestamp [UTC]: 2026-06-09 14:14:58 | Age [y:d:h:m:s]: 00:007:19:00:08 |
| Block: 8621 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 124 | RingCT/type: yes/0 |
| Extra: 0166b951167ca0a0f30633278906c9358391276c7a457c1196d320d2e30dc62cb1020900000005e49593ff00 | ||
1 output(s) for total of 34.610622664780 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1960e34e877d56b4342fc8b76c4e9d86f068109c49f45b79208e03b9df3319e5 | 34.610622664780 | 10655 of 0 | <d1> |
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": 8681,
"vin": [ {
"gen": {
"height": 8621
}
}
],
"vout": [ {
"amount": 34610622664780,
"target": {
"tagged_key": {
"key": "1960e34e877d56b4342fc8b76c4e9d86f068109c49f45b79208e03b9df3319e5",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 102, 185, 81, 22, 124, 160, 160, 243, 6, 51, 39, 137, 6, 201, 53, 131, 145, 39, 108, 122, 69, 124, 17, 150, 211, 32, 210, 227, 13, 198, 44, 177, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}