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: ed0c1f6d47240e015fc773e8de3042cec497d122823eebdfad3b810447787936
Tx prefix hash: e2cb0d79f763c0bbf84ede50a0aebfff82b2d2ddf1bb3a6a5ba9c77db3448afe
Tx public key: 35aa7a271c044fae5682df147df376962f8327ed9fd8dc83ee262d3568e328df
| Timestamp: 1780766547 | Timestamp [UTC]: 2026-06-06 17:22:27 | Age [y:d:h:m:s]: 00:002:08:13:30 |
| Block: 6620 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1266 | RingCT/type: yes/0 |
| Extra: 0135aa7a271c044fae5682df147df376962f8327ed9fd8dc83ee262d3568e328df020900000002e49593ff00 | ||
1 output(s) for total of 34.747194251714 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7e95165b489243698a86b420da84708de6bb2e1e16a4b541c7aec6b2be03692 | 34.747194251714 | 8158 of 0 | <94> |
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": 6680,
"vin": [ {
"gen": {
"height": 6620
}
}
],
"vout": [ {
"amount": 34747194251714,
"target": {
"tagged_key": {
"key": "d7e95165b489243698a86b420da84708de6bb2e1e16a4b541c7aec6b2be03692",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 53, 170, 122, 39, 28, 4, 79, 174, 86, 130, 223, 20, 125, 243, 118, 150, 47, 131, 39, 237, 159, 216, 220, 131, 238, 38, 45, 53, 104, 227, 40, 223, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}