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: 1378097ca33686a663aa17dfb28ea4e77b18f7173d20e46b2153a7c18b8b3b0d
Tx prefix hash: a0f7903bef16915779fc18cae3e357ffb4d9b4b1ee9023b42f3a145becec223d
Tx public key: 278c320fdbf610cdc1f35dae06b63b622acb87ea44e30a7e2d3d5e62f6e3bf06
| Timestamp: 1781018808 | Timestamp [UTC]: 2026-06-09 15:26:48 | Age [y:d:h:m:s]: 00:006:05:00:10 |
| Block: 8666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 79 | RingCT/type: yes/0 |
| Extra: 01278c320fdbf610cdc1f35dae06b63b622acb87ea44e30a7e2d3d5e62f6e3bf06020900000001e49593ff00 | ||
1 output(s) for total of 34.607652135859 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d42055ebe30bc6459553c7a3bd57e8bda978f068958dcfe118976b4fca13a73 | 34.607652135859 | 10714 of 0 | <fd> |
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": 8726,
"vin": [ {
"gen": {
"height": 8666
}
}
],
"vout": [ {
"amount": 34607652135859,
"target": {
"tagged_key": {
"key": "9d42055ebe30bc6459553c7a3bd57e8bda978f068958dcfe118976b4fca13a73",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 39, 140, 50, 15, 219, 246, 16, 205, 193, 243, 93, 174, 6, 182, 59, 98, 42, 203, 135, 234, 68, 227, 10, 126, 45, 61, 94, 98, 246, 227, 191, 6, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}