Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d12382cf262fdd4072f1026e0e349165928aae37db4da95b568a9a8dcb6449a2

Tx prefix hash: 1b030c6435faf8cb9e1f7ee18eef5088976df6991a5741677dce8c6a4ecd7895
Tx public key: ef7efd45367c9fc0c95c4da35995fadfc2547f940e37109a3ab6e3689f14d26a
Timestamp: 1750596315 Timestamp [UCT]: 2025-06-22 12:45:15 Age [y:d:h:m:s]: 00:151:19:00:46
Block: 1310450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106350 RingCT/type: yes/0
Extra: 01ef7efd45367c9fc0c95c4da35995fadfc2547f940e37109a3ab6e3689f14d26a02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac535c43d7984d517ebef0184a3b150ea9e8b05bbaf8d418ac044c23a73dc029 0.600000000000 1798071 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": 1310460, "vin": [ { "gen": { "height": 1310450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac535c43d7984d517ebef0184a3b150ea9e8b05bbaf8d418ac044c23a73dc029" } } ], "extra": [ 1, 239, 126, 253, 69, 54, 124, 159, 192, 201, 92, 77, 163, 89, 149, 250, 223, 194, 84, 127, 148, 14, 55, 16, 154, 58, 182, 227, 104, 159, 20, 210, 106, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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