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: 4357c13af19cdd2b9899274e5717df24a8734224bd4c2671b8812f9948251614
Tx prefix hash: dc70caea131cf16f60d3818771dda6275d476248c6c48fe9c0431282f5c15454
Tx public key: c3a1c69fc004c82b6d2b7c15a3fc864fcb474012ea701e52e41b9e10f63d9283
| Timestamp: 1780748192 | Timestamp [UTC]: 2026-06-06 12:16:32 | Age [y:d:h:m:s]: 00:002:11:02:21 |
| Block: 6464 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1422 | RingCT/type: yes/0 |
| Extra: 01c3a1c69fc004c82b6d2b7c15a3fc864fcb474012ea701e52e41b9e10f63d9283020900000001e49593ff00 | ||
1 output(s) for total of 34.753309444955 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0d9223a7aa03c0561dfa3099bc7e68542d0f594ace293578bbca267e2ec070a7 | 34.753309444955 | 7959 of 0 | <6a> |
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": 6524,
"vin": [ {
"gen": {
"height": 6464
}
}
],
"vout": [ {
"amount": 34753309444955,
"target": {
"tagged_key": {
"key": "0d9223a7aa03c0561dfa3099bc7e68542d0f594ace293578bbca267e2ec070a7",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 195, 161, 198, 159, 192, 4, 200, 43, 109, 43, 124, 21, 163, 252, 134, 79, 203, 71, 64, 18, 234, 112, 30, 82, 228, 27, 158, 16, 246, 61, 146, 131, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}