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: 9034a0786668bbeebbb13a4bc5bc22c75bd5d38cdd98147a68130195ea40cf48
Tx prefix hash: a634e330a35ac52434b53150d23bfae40d18b9872fe21c261a8f183bb2d0bb40
Tx public key: 832b799beab5bce745f80faee68b4c227909b45a12e3adeea15378c37a9ec5e5
| Timestamp: 1780688206 | Timestamp [UTC]: 2026-06-05 19:36:46 | Age [y:d:h:m:s]: 00:003:03:42:07 |
| Block: 5516 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2370 | RingCT/type: yes/0 |
| Extra: 01832b799beab5bce745f80faee68b4c227909b45a12e3adeea15378c37a9ec5e5020900000001e49593ff00 | ||
1 output(s) for total of 34.816206121672 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43593fb9bf8e1d71fae0bd852a3d8d49ce3352d421cbc83ac75de09e8d7aeef9 | 34.816206121672 | 6957 of 0 | <dc> |
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": 5576,
"vin": [ {
"gen": {
"height": 5516
}
}
],
"vout": [ {
"amount": 34816206121672,
"target": {
"tagged_key": {
"key": "43593fb9bf8e1d71fae0bd852a3d8d49ce3352d421cbc83ac75de09e8d7aeef9",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 131, 43, 121, 155, 234, 181, 188, 231, 69, 248, 15, 174, 230, 139, 76, 34, 121, 9, 180, 90, 18, 227, 173, 238, 161, 83, 120, 195, 122, 158, 197, 229, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}