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: e9a0cdc5af02ebad0b89e4b4ce11bfc142fea5242cab4354a3c37f198c192c84
Tx prefix hash: ae0ae9a6de72613fd969d1b92b76d515fe9ed62312cfb23ad274ce7d5a23b242
Tx public key: ee7d9d8f14c0d5c2c7f6367f6e9df7611cfd9a6c55b8de4e53b70c48bac62bda
| Timestamp: 1780904810 | Timestamp [UTC]: 2026-06-08 07:46:50 | Age [y:d:h:m:s]: 00:000:13:25:17 |
| Block: 7855 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 31 | RingCT/type: yes/0 |
| Extra: 01ee7d9d8f14c0d5c2c7f6367f6e9df7611cfd9a6c55b8de4e53b70c48bac62bda0209000000014a728a4c00 | ||
1 output(s) for total of 34.661226796338 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3fc3b53be67a7cbd746f8bbbb5dde4e67e266f89bd0958eea2a67d728e9f4dc | 34.661226796338 | 9739 of 0 | <d4> |
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": 7915,
"vin": [ {
"gen": {
"height": 7855
}
}
],
"vout": [ {
"amount": 34661226796338,
"target": {
"tagged_key": {
"key": "c3fc3b53be67a7cbd746f8bbbb5dde4e67e266f89bd0958eea2a67d728e9f4dc",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 238, 125, 157, 143, 20, 192, 213, 194, 199, 246, 54, 127, 110, 157, 247, 97, 28, 253, 154, 108, 85, 184, 222, 78, 83, 183, 12, 72, 186, 198, 43, 218, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}