Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1b67a981ff437487a7d3a1f2cbf837036502917cd066ccbfd99d8a5c29ad8de0

Tx prefix hash: 9e20831b6afe4d527280d772a302c714d12f48ef026d15d9be40ea2e9171291c
Tx public key: 825a849a2324da4be4486b37248d2eed54f0bdcd86668d21d857f219e9e9c863
Timestamp: 1708766997 Timestamp [UCT]: 2024-02-24 09:29:57 Age [y:d:h:m:s]: 01:044:23:58:49
Block: 964435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293176 RingCT/type: yes/0
Extra: 01825a849a2324da4be4486b37248d2eed54f0bdcd86668d21d857f219e9e9c86302110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5bef1d81d604e6c6b5fa5d1eda17be6af772036add95a93cfe96e83bc8b294a 0.600000000000 1424170 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 964445, "vin": [ { "gen": { "height": 964435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5bef1d81d604e6c6b5fa5d1eda17be6af772036add95a93cfe96e83bc8b294a" } } ], "extra": [ 1, 130, 90, 132, 154, 35, 36, 218, 75, 228, 72, 107, 55, 36, 141, 46, 237, 84, 240, 189, 205, 134, 102, 141, 33, 216, 87, 242, 25, 233, 233, 200, 99, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8