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: 60f64f0fe93f936b5eece1caad09c7ccd1990cc76fa958798559b484f78296a0
Tx prefix hash: 22ef339e11006409e8e3497eeab0a6db7ba409afe8904f2463b9c83e0512afe1
Tx public key: 143552ebf0096ef6819dc779fd46b4606dc22dccd096975bc5059a259df11f08
| Timestamp: 1779648816 | Timestamp [UTC]: 2026-05-24 18:53:36 | Age [y:d:h:m:s]: 00:015:07:47:00 |
| Block: 1470 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6426 | RingCT/type: yes/0 |
| Extra: 01143552ebf0096ef6819dc779fd46b4606dc22dccd096975bc5059a259df11f08020900000002ba6d17be00 | ||
1 output(s) for total of 35.085927054581 HMNY
| stealth address | amount | amount idx | tag |
| 00: f39bca7a8fa5d7c62d1651b7be746645bec5efb59c22f439c6ccf9df9812d3a0 | 35.085927054581 | 1624 of 0 | <04> |
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": 1530,
"vin": [ {
"gen": {
"height": 1470
}
}
],
"vout": [ {
"amount": 35085927054581,
"target": {
"tagged_key": {
"key": "f39bca7a8fa5d7c62d1651b7be746645bec5efb59c22f439c6ccf9df9812d3a0",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 20, 53, 82, 235, 240, 9, 110, 246, 129, 157, 199, 121, 253, 70, 180, 96, 109, 194, 45, 204, 208, 150, 151, 91, 197, 5, 154, 37, 157, 241, 31, 8, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}