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: e13867805da78f72aaeefa9cc7658f54014e5ae74daa2c6fa411fc23f46d3dbe
Tx prefix hash: cb32f6410b3d343bb509a3f9a7e2685ee75b5356bde160a13211796be24324ba
Tx public key: 63beaf5de2f508c891210866d2626fbcd5fd7f922d2009641cb93e460ac0ccf8
| Timestamp: 1780758179 | Timestamp [UTC]: 2026-06-06 15:02:59 | Age [y:d:h:m:s]: 00:008:21:37:10 |
| Block: 6550 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2195 | RingCT/type: yes/0 |
| Extra: 0163beaf5de2f508c891210866d2626fbcd5fd7f922d2009641cb93e460ac0ccf8020900000005e49593ff00 | ||
1 output(s) for total of 34.747609252794 HMNY
| stealth address | amount | amount idx | tag |
| 00: e94108759ccee78f7b2137827b174fcd7c96e3348182bfa90bfd4eca52b5d282 | 34.747609252794 | 8062 of 0 | <e0> |
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": 6610,
"vin": [ {
"gen": {
"height": 6550
}
}
],
"vout": [ {
"amount": 34747609252794,
"target": {
"tagged_key": {
"key": "e94108759ccee78f7b2137827b174fcd7c96e3348182bfa90bfd4eca52b5d282",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 99, 190, 175, 93, 226, 245, 8, 200, 145, 33, 8, 102, 210, 98, 111, 188, 213, 253, 127, 146, 45, 32, 9, 100, 28, 185, 62, 70, 10, 192, 204, 248, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}