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: c5a202d980a684b6858399f39d75b358d44ac963ae7807ffa83612b9cb5da095
Tx prefix hash: 1ce7c84f58f4c9fa440f8aeea85e7f9a5a3f4a4b8169339a4f8a4153832d92fa
Tx public key: 2aaecf1b83f36d30294ea2faf9a2417cbc818da6c8070cfbc36955da78b57e92
| Timestamp: 1780982331 | Timestamp [UTC]: 2026-06-09 05:18:51 | Age [y:d:h:m:s]: 00:000:09:30:04 |
| Block: 8060 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 597 | RingCT/type: yes/0 |
| Extra: 012aaecf1b83f36d30294ea2faf9a2417cbc818da6c8070cfbc36955da78b57e92020900000001e49593ff00 | ||
1 output(s) for total of 34.647676668756 HMNY
| stealth address | amount | amount idx | tag |
| 00: de1bccaf502a9144f25838dc676cffe0e870ae6b9f9b231c68883e72cc340ed1 | 34.647676668756 | 9988 of 0 | <79> |
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": 8120,
"vin": [ {
"gen": {
"height": 8060
}
}
],
"vout": [ {
"amount": 34647676668756,
"target": {
"tagged_key": {
"key": "de1bccaf502a9144f25838dc676cffe0e870ae6b9f9b231c68883e72cc340ed1",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 42, 174, 207, 27, 131, 243, 109, 48, 41, 78, 162, 250, 249, 162, 65, 124, 188, 129, 141, 166, 200, 7, 12, 251, 195, 105, 85, 218, 120, 181, 126, 146, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}