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: 0d4c05add4d799576f5e6315cd0b4e86d26772041c65d8f88264b5e915280f92
Tx prefix hash: 1e01d86f9ec0dfab9da3177f6332c2fe9a337b39ed82d8e35ac75a4184d3cb05
Tx public key: 4f90257a30b1c3c2977a9a1266bf54d76da963ef613d8b51315d43d1e47b304d
| Timestamp: 1780323393 | Timestamp [UTC]: 2026-06-01 14:16:33 | Age [y:d:h:m:s]: 00:015:18:58:33 |
| Block: 5128 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3617 | RingCT/type: yes/0 |
| Extra: 014f90257a30b1c3c2977a9a1266bf54d76da963ef613d8b51315d43d1e47b304d02090000005426697be300 | ||
1 output(s) for total of 34.841981460153 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd152483d769e2992f0a961a5f383d98a07eb50cfade2b565c3b92e648ba0e3f | 34.841981460153 | 6503 of 0 | <e1> |
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": 5188,
"vin": [ {
"gen": {
"height": 5128
}
}
],
"vout": [ {
"amount": 34841981460153,
"target": {
"tagged_key": {
"key": "dd152483d769e2992f0a961a5f383d98a07eb50cfade2b565c3b92e648ba0e3f",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 79, 144, 37, 122, 48, 177, 195, 194, 151, 122, 154, 18, 102, 191, 84, 215, 109, 169, 99, 239, 97, 61, 139, 81, 49, 93, 67, 209, 228, 123, 48, 77, 2, 9, 0, 0, 0, 84, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}