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: dde6cf3e3d9a788d9837fe3ad41881e9dfdcefd6a0cec289a9c31bb92af12792
Tx prefix hash: 254f104ac2f08c8acb2ccc17f63f462423aa58e4002d190e48a9386a9d9e9a3b
Tx public key: 11795ca53fa279bc1ad4d58e8cdc9f0131ad12e4e348827e902ff1fca90aa667
| Timestamp: 1780994833 | Timestamp [UTC]: 2026-06-09 08:47:13 | Age [y:d:h:m:s]: 00:000:06:01:42 |
| Block: 8311 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 344 | RingCT/type: yes/0 |
| Extra: 0111795ca53fa279bc1ad4d58e8cdc9f0131ad12e4e348827e902ff1fca90aa667020900000002e49593ff00 | ||
1 output(s) for total of 34.631093237991 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe53959a786f570386ae93bc76577d06278352793c4009a149fcbf2d523e77ae | 34.631093237991 | 10281 of 0 | <8d> |
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": 8371,
"vin": [ {
"gen": {
"height": 8311
}
}
],
"vout": [ {
"amount": 34631093237991,
"target": {
"tagged_key": {
"key": "fe53959a786f570386ae93bc76577d06278352793c4009a149fcbf2d523e77ae",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 17, 121, 92, 165, 63, 162, 121, 188, 26, 212, 213, 142, 140, 220, 159, 1, 49, 173, 18, 228, 227, 72, 130, 126, 144, 47, 241, 252, 169, 10, 166, 103, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}