Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6809500e4d8fe23403c9fa8061281d1fc3853164c32ef82846d8c17153f75a9d

Tx prefix hash: 0314ac5dd2ddf54f166c2f837c1e5d5a10fbc977086eeb06a793880550ed8d2a
Tx public key: 20dc3df40fd2c2f1174df6d431a7952797d29aaf47bdb9fe108049f4e3f27735
Timestamp: 1708049903 Timestamp [UCT]: 2024-02-16 02:18:23 Age [y:d:h:m:s]: 01:047:23:31:09
Block: 958474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295321 RingCT/type: yes/0
Extra: 0120dc3df40fd2c2f1174df6d431a7952797d29aaf47bdb9fe108049f4e3f277350211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d1545a06357dcdba9bdd593f07163dcae083aa3c77fc6fcbbe652f408edd40e 0.600000000000 1417833 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": 958484, "vin": [ { "gen": { "height": 958474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1545a06357dcdba9bdd593f07163dcae083aa3c77fc6fcbbe652f408edd40e" } } ], "extra": [ 1, 32, 220, 61, 244, 15, 210, 194, 241, 23, 77, 246, 212, 49, 167, 149, 39, 151, 210, 154, 175, 71, 189, 185, 254, 16, 128, 73, 244, 227, 242, 119, 53, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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