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: 400463a41a378153a561c5749661318542a2b3b484e2d6a749a6804066bd2574
Tx prefix hash: 060c9a1ef555f35a5342c5092cb0ce7e5e1acb5759a2abe3d41b0f67b800ee9c
Tx public key: 42e699706f0818964a1c1759b17913b40f161338781b7e342f5b93158d39fe10
| Timestamp: 1779956801 | Timestamp [UTC]: 2026-05-28 08:26:41 | Age [y:d:h:m:s]: 00:011:14:52:12 |
| Block: 3704 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4182 | RingCT/type: yes/0 |
| Extra: 0142e699706f0818964a1c1759b17913b40f161338781b7e342f5b93158d39fe1002090000000326697be300 | ||
1 output(s) for total of 34.936743249154 HMNY
| stealth address | amount | amount idx | tag |
| 00: d68c7ba7085c6c02df879b4122d9f0a589abec5370ed00d0a094af5bdd6f1b02 | 34.936743249154 | 4480 of 0 | <d4> |
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": 3764,
"vin": [ {
"gen": {
"height": 3704
}
}
],
"vout": [ {
"amount": 34936743249154,
"target": {
"tagged_key": {
"key": "d68c7ba7085c6c02df879b4122d9f0a589abec5370ed00d0a094af5bdd6f1b02",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 66, 230, 153, 112, 111, 8, 24, 150, 74, 28, 23, 89, 177, 121, 19, 180, 15, 22, 19, 56, 120, 27, 126, 52, 47, 91, 147, 21, 141, 57, 254, 16, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}