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: 54c279d7dbe1479f915e29be009a60e0269acc9c108f1c8b1a0bcca18f6b8601
Tx prefix hash: bfe4a7c050b6903334e2ba6d34154824b9d837355bbc4b18e1bde7867e779bb3
Tx public key: 42ab48ee78e8d1d39a33eccad17afeaac5aeb6a5480cada302ea0c19e8ee3be1
| Timestamp: 1779714135 | Timestamp [UTC]: 2026-05-25 13:02:15 | Age [y:d:h:m:s]: 00:014:10:16:38 |
| Block: 1612 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6274 | RingCT/type: yes/0 |
| Extra: 0142ab48ee78e8d1d39a33eccad17afeaac5aeb6a5480cada302ea0c19e8ee3be1020900000001ba6d17be00 | ||
1 output(s) for total of 35.076425536800 HMNY
| stealth address | amount | amount idx | tag |
| 00: fcdb26163ab537ef6291b9a8166686396a7d7d7eb36174d6c448461be0eb48be | 35.076425536800 | 1770 of 0 | <22> |
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": 1672,
"vin": [ {
"gen": {
"height": 1612
}
}
],
"vout": [ {
"amount": 35076425536800,
"target": {
"tagged_key": {
"key": "fcdb26163ab537ef6291b9a8166686396a7d7d7eb36174d6c448461be0eb48be",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 66, 171, 72, 238, 120, 232, 209, 211, 154, 51, 236, 202, 209, 122, 254, 170, 197, 174, 182, 165, 72, 12, 173, 163, 2, 234, 12, 25, 232, 238, 59, 225, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}