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: 7bcbe2f559f24724055ebe9bce2aff267050f9425039bd2588ebe40832bf2aa3
Tx prefix hash: fc9b2929beab4750f9cf621d9de680edbf28a76dfe8ab288a583fa3f9c7d45d3
Tx public key: c978ee65a39794cfa63b64733b9bc9a4ba64269cefa42d3b2161e942f7d1b14b
| Timestamp: 1780713883 | Timestamp [UTC]: 2026-06-06 02:44:43 | Age [y:d:h:m:s]: 00:002:22:02:04 |
| Block: 6177 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1709 | RingCT/type: yes/0 |
| Extra: 01c978ee65a39794cfa63b64733b9bc9a4ba64269cefa42d3b2161e942f7d1b14b020900000002e49593ff00 | ||
1 output(s) for total of 34.772338947461 HMNY
| stealth address | amount | amount idx | tag |
| 00: e31710f288d0ac631b0b3cbd8923e114f65ed781160349f0a28a85dcaf97da58 | 34.772338947461 | 7654 of 0 | <a1> |
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": 6237,
"vin": [ {
"gen": {
"height": 6177
}
}
],
"vout": [ {
"amount": 34772338947461,
"target": {
"tagged_key": {
"key": "e31710f288d0ac631b0b3cbd8923e114f65ed781160349f0a28a85dcaf97da58",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 201, 120, 238, 101, 163, 151, 148, 207, 166, 59, 100, 115, 59, 155, 201, 164, 186, 100, 38, 156, 239, 164, 45, 59, 33, 97, 233, 66, 247, 209, 177, 75, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}