Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a718a353a67b580ce2f8ba333ebdbaca906a8655dc452759ed942c55feabec7

Tx prefix hash: 78583585ebe746d43a552a8c3dc28bbfaf47c9f48f3d87b955b371be77189e16
Tx public key: d304346f1182781e1b06009f3f3ea016cd6d4b71573da1e78b94dd971cdd92eb
Timestamp: 1577187542 Timestamp [UCT]: 2019-12-24 11:39:02 Age [y:d:h:m:s]: 05:071:13:21:22
Block: 30652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200950 RingCT/type: yes/0
Extra: 01d304346f1182781e1b06009f3f3ea016cd6d4b71573da1e78b94dd971cdd92eb0211000000044ac5aa02000000000000000000

1 output(s) for total of 485.791954480000 dcy

stealth address amount amount idx
00: bd1bfe773dc392b0987d64952f3dcda82622d591e82231b347d15ff20f02e3a9 485.791954480000 50610 of 0

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": 30662, "vin": [ { "gen": { "height": 30652 } } ], "vout": [ { "amount": 485791954480, "target": { "key": "bd1bfe773dc392b0987d64952f3dcda82622d591e82231b347d15ff20f02e3a9" } } ], "extra": [ 1, 211, 4, 52, 111, 17, 130, 120, 30, 27, 6, 0, 159, 63, 62, 160, 22, 205, 109, 75, 113, 87, 61, 161, 231, 139, 148, 221, 151, 28, 221, 146, 235, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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