Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20df8c8e35e59eb6111057da0ed74c3b4b19ddf5681e5c9a36543edfce589c9e

Tx prefix hash: f62e7542ca8bf95ac9ad8b5edfb9260b3a79f9f2acfedf4aa99fdb877bfc1a2a
Tx public key: 78653c518c5b9a8a5e792ef82e061d0800f6e6e423e251b524f9c816945dcb68
Timestamp: 1737568147 Timestamp [UCT]: 2025-01-22 17:49:07 Age [y:d:h:m:s]: 00:145:12:27:36
Block: 1203011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103751 RingCT/type: yes/0
Extra: 0178653c518c5b9a8a5e792ef82e061d0800f6e6e423e251b524f9c816945dcb68021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7683db8379016a23207b9f8b3667657c86a98f614b3ed22d0f201e54600f25d0 0.600000000000 1689682 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": 1203021, "vin": [ { "gen": { "height": 1203011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7683db8379016a23207b9f8b3667657c86a98f614b3ed22d0f201e54600f25d0" } } ], "extra": [ 1, 120, 101, 60, 81, 140, 91, 154, 138, 94, 121, 46, 248, 46, 6, 29, 8, 0, 246, 230, 228, 35, 226, 81, 181, 36, 249, 200, 22, 148, 93, 203, 104, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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