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: 88a45cf76b58a4b3220d6d95e4d9207c8ba3ee23c57d65380cc69b46a67a47b7
Tx prefix hash: 95e8675b1ee86ae30e52268ae543c82e14c7b0cd59ce3ae0c161dc8699386346
Tx public key: b875e4cd9f7cb738461daf9c77de75896e403a5c6bc5e5695482771638deba64
| Timestamp: 1780748036 | Timestamp [UTC]: 2026-06-06 12:13:56 | Age [y:d:h:m:s]: 00:008:20:05:39 |
| Block: 6462 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2283 | RingCT/type: yes/0 |
| Extra: 01b875e4cd9f7cb738461daf9c77de75896e403a5c6bc5e5695482771638deba64020900000002e49593ff00 | ||
1 output(s) for total of 34.753442018689 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5805ffc2a7fdabdba74e69774f26027ea8480f8be8994b16f892afee92fa09c4 | 34.753442018689 | 7957 of 0 | <2d> |
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": 6522,
"vin": [ {
"gen": {
"height": 6462
}
}
],
"vout": [ {
"amount": 34753442018689,
"target": {
"tagged_key": {
"key": "5805ffc2a7fdabdba74e69774f26027ea8480f8be8994b16f892afee92fa09c4",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 184, 117, 228, 205, 159, 124, 183, 56, 70, 29, 175, 156, 119, 222, 117, 137, 110, 64, 58, 92, 107, 197, 229, 105, 84, 130, 119, 22, 56, 222, 186, 100, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}