Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f20947c09493f40552c3216bf9510996123e75b5d9bdc75e173041c75f0021

Tx prefix hash: 0f0a50d09e5a9fe46a22ad9dcc0ee5a3abdcf0f9d149ca0beb0328a2546b5c1a
Tx public key: 897ec0219fab5b4d9930fc524371c2c517067c6c781009565ef2ca1770520e6f
Timestamp: 1750638461 Timestamp [UCT]: 2025-06-23 00:27:41 Age [y:d:h:m:s]: 00:143:13:15:36
Block: 1310783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100480 RingCT/type: yes/0
Extra: 01897ec0219fab5b4d9930fc524371c2c517067c6c781009565ef2ca1770520e6f021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29d155807fd9e7b9dcb73bed0d182ba02e32f753260a098c66a868c6a2df4843 0.600000000000 1798406 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": 1310793, "vin": [ { "gen": { "height": 1310783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29d155807fd9e7b9dcb73bed0d182ba02e32f753260a098c66a868c6a2df4843" } } ], "extra": [ 1, 137, 126, 192, 33, 159, 171, 91, 77, 153, 48, 252, 82, 67, 113, 194, 197, 23, 6, 124, 108, 120, 16, 9, 86, 94, 242, 202, 23, 112, 82, 14, 111, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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