Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354e85bc6bf3fd70b9ff657bd3a6332ad035ca76e5d99f85b2968db1acacc884

Tx prefix hash: 6cada6ac70a1e0ada5394f75425f352d9a739d937dac2b73ec56c75438e7c430
Tx public key: f63348ea335c46567998d3c1ee7a47d44566020b8c87b8cb0e49aa8ccaeb9dfc
Timestamp: 1756659291 Timestamp [UCT]: 2025-08-31 16:54:51 Age [y:d:h:m:s]: 00:125:03:42:39
Block: 1358498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89503 RingCT/type: yes/0
Extra: 01f63348ea335c46567998d3c1ee7a47d44566020b8c87b8cb0e49aa8ccaeb9dfc021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffd1a51b0441fcc1b074ea0f0469b7a2299c4fec65cc95ed7ad4830608cca521 0.600000000000 1846511 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": 1358508, "vin": [ { "gen": { "height": 1358498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffd1a51b0441fcc1b074ea0f0469b7a2299c4fec65cc95ed7ad4830608cca521" } } ], "extra": [ 1, 246, 51, 72, 234, 51, 92, 70, 86, 121, 152, 211, 193, 238, 122, 71, 212, 69, 102, 2, 11, 140, 135, 184, 203, 14, 73, 170, 140, 202, 235, 157, 252, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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