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: a75311f054a750fafce98ab5fdb258a7cf03ce1686c699224c117dde2f8c4dcc
Tx prefix hash: 22c17a098cc9ca4c79bfc355f0e715a9ff2c88748c66b95de88b8ffea3963c68
Tx public key: 10df6024a1857430324d5351b4289e9f9189888d3d2df322f67658c94c95e218
| Timestamp: 1780138513 | Timestamp [UTC]: 2026-05-30 10:55:13 | Age [y:d:h:m:s]: 00:009:15:54:35 |
| Block: 4978 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2942 | RingCT/type: yes/0 |
| Extra: 0110df6024a1857430324d5351b4289e9f9189888d3d2df322f67658c94c95e21802090000000426697be300 | ||
1 output(s) for total of 34.851951266641 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5963fe9f5e99decbb61d38788c65b84dac7980d9cac54d18419631c5ae4fa486 | 34.851951266641 | 6335 of 0 | <da> |
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": 5038,
"vin": [ {
"gen": {
"height": 4978
}
}
],
"vout": [ {
"amount": 34851951266641,
"target": {
"tagged_key": {
"key": "5963fe9f5e99decbb61d38788c65b84dac7980d9cac54d18419631c5ae4fa486",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 16, 223, 96, 36, 161, 133, 116, 48, 50, 77, 83, 81, 180, 40, 158, 159, 145, 137, 136, 141, 61, 45, 243, 34, 246, 118, 88, 201, 76, 149, 226, 24, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}