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: f2c28fdffc42bc988906265a3da4b5636a1e1990a895c1259f714c2c7ff912ce
Tx prefix hash: 4249be74cbe9d3ff188ed4777595f2c8aaa53f1b80cbf0651f54f5e59133f256
Tx public key: 1663699557c3942b439bfd6d016f28b5d5381c6c3af58c6d49d29fad6c6f145d
| Timestamp: 1780764342 | Timestamp [UTC]: 2026-06-06 16:45:42 | Age [y:d:h:m:s]: 00:003:00:23:21 |
| Block: 6603 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2132 | RingCT/type: yes/0 |
| Extra: 011663699557c3942b439bfd6d016f28b5d5381c6c3af58c6d49d29fad6c6f145d020900000002e49593ff00 | ||
1 output(s) for total of 34.744096809318 HMNY
| stealth address | amount | amount idx | tag |
| 00: dbeb4763ded5560ef9439e5f4597565b93e4937bca977eed5fb744cb97eca84b | 34.744096809318 | 8135 of 0 | <1a> |
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": 6663,
"vin": [ {
"gen": {
"height": 6603
}
}
],
"vout": [ {
"amount": 34744096809318,
"target": {
"tagged_key": {
"key": "dbeb4763ded5560ef9439e5f4597565b93e4937bca977eed5fb744cb97eca84b",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 22, 99, 105, 149, 87, 195, 148, 43, 67, 155, 253, 109, 1, 111, 40, 181, 213, 56, 28, 108, 58, 245, 140, 109, 73, 210, 159, 173, 108, 111, 20, 93, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}