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: 0dfcd41d6b7174f8f9864b893a0deb8409fda09bb55b2c378be29993ddda10dc
Tx prefix hash: 80ea5c656f5a1bf8df19ed13c7f499dbd5f9a3ce271cb3c52501ec8f134adec9
Tx public key: 4ccab3e0d6b3a2bdfda3d49fa34f0173263011f37e4f81a505a4db2f64f4e33f
| Timestamp: 1779873788 | Timestamp [UTC]: 2026-05-27 09:23:08 | Age [y:d:h:m:s]: 00:012:18:27:50 |
| Block: 2848 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5133 | RingCT/type: yes/0 |
| Extra: 014ccab3e0d6b3a2bdfda3d49fa34f0173263011f37e4f81a505a4db2f64f4e33f02090000000126697be300 | ||
1 output(s) for total of 34.993830780396 HMNY
| stealth address | amount | amount idx | tag |
| 00: 825d904b2c35c0337f065c46161b205ad703091b71a077a809e084f47e9877f5 | 34.993830780396 | 3372 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": 2908,
"vin": [ {
"gen": {
"height": 2848
}
}
],
"vout": [ {
"amount": 34993830780396,
"target": {
"tagged_key": {
"key": "825d904b2c35c0337f065c46161b205ad703091b71a077a809e084f47e9877f5",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 76, 202, 179, 224, 214, 179, 162, 189, 253, 163, 212, 159, 163, 79, 1, 115, 38, 48, 17, 243, 126, 79, 129, 165, 5, 164, 219, 47, 100, 244, 227, 63, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}