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: 316b53bcfa2b33a0b623314524f4469b939e5fb2990d1c345d7986b8932941ea
Tx prefix hash: 41c7c2be1e83825a8e8aeb6b744f16fb62f478f5925f8a2e7d0d24a4a20bef47
Tx public key: 8b7c6639c2fff0af6c2d122df154ac67b268da0468fa17a22dbd664903de74ed
| Timestamp: 1779787196 | Timestamp [UTC]: 2026-05-26 09:19:56 | Age [y:d:h:m:s]: 00:013:17:20:40 |
| Block: 2179 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5718 | RingCT/type: yes/0 |
| Extra: 018b7c6639c2fff0af6c2d122df154ac67b268da0468fa17a22dbd664903de74ed02090000000226697be300 | ||
1 output(s) for total of 35.038512020151 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25915fa27831b4d78a9e94574d5c132899c5b0bf327c7c71183209e350da036c | 35.038512020151 | 2519 of 0 | <7d> |
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": 2239,
"vin": [ {
"gen": {
"height": 2179
}
}
],
"vout": [ {
"amount": 35038512020151,
"target": {
"tagged_key": {
"key": "25915fa27831b4d78a9e94574d5c132899c5b0bf327c7c71183209e350da036c",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 139, 124, 102, 57, 194, 255, 240, 175, 108, 45, 18, 45, 241, 84, 172, 103, 178, 104, 218, 4, 104, 250, 23, 162, 45, 189, 102, 73, 3, 222, 116, 237, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}