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: d49fc7416499706d7e168dbce9eae02d8a45750b2c8b793e6504c5dc985f85eb
Tx prefix hash: 98f208d697c8f7db28c7d5fad2030bc8e08b3b91314daa37385e99381e0abe62
Tx public key: a244c7c8d34c4fbaef63ead575f72c564ddcd6a23f29285809b85493b4550382
| Timestamp: 1780718809 | Timestamp [UTC]: 2026-06-06 04:06:49 | Age [y:d:h:m:s]: 00:002:23:32:01 |
| Block: 6219 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1723 | RingCT/type: yes/0 |
| Extra: 01a244c7c8d34c4fbaef63ead575f72c564ddcd6a23f29285809b85493b4550382020900000001e49593ff00 | ||
1 output(s) for total of 34.769553491503 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f100f152828eaeb97f76b32c6a66335a86579aaa169952a6326ffdff05234f0 | 34.769553491503 | 7698 of 0 | <ee> |
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": 6279,
"vin": [ {
"gen": {
"height": 6219
}
}
],
"vout": [ {
"amount": 34769553491503,
"target": {
"tagged_key": {
"key": "7f100f152828eaeb97f76b32c6a66335a86579aaa169952a6326ffdff05234f0",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 162, 68, 199, 200, 211, 76, 79, 186, 239, 99, 234, 213, 117, 247, 44, 86, 77, 220, 214, 162, 63, 41, 40, 88, 9, 184, 84, 147, 180, 85, 3, 130, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}