Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 682d6f70910f53a63a4c0e8ed781c5e39e82b942d06dc6f1f42b99f4ee6b772e

Tx prefix hash: d9966225bec2aa1ec7ad2a20798f443d054c66321ffa8b0d10ee817993029ee8
Tx public key: 00abf2aeeb7e565936ed1f5bf70f4f02af6c7208323612670c71473ea05c36aa
Timestamp: 1766225823 Timestamp [UCT]: 2025-12-20 10:17:03 Age [y:d:h:m:s]: 00:002:02:43:25
Block: 1437662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1508 RingCT/type: yes/0
Extra: 0100abf2aeeb7e565936ed1f5bf70f4f02af6c7208323612670c71473ea05c36aa0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb00b09ba2dbdf6d7791a789649b2bc4266206e0c3d5662c0924d929cc09b002 0.600000000000 1926471 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": 1437672, "vin": [ { "gen": { "height": 1437662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb00b09ba2dbdf6d7791a789649b2bc4266206e0c3d5662c0924d929cc09b002" } } ], "extra": [ 1, 0, 171, 242, 174, 235, 126, 86, 89, 54, 237, 31, 91, 247, 15, 79, 2, 175, 108, 114, 8, 50, 54, 18, 103, 12, 113, 71, 62, 160, 92, 54, 170, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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