Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d4b1d4151a0aa2365cc8d016a8455aca0387a5758b34f9de66f4c4d7352c4c

Tx prefix hash: ef45650e49cec0b628cbac4921d546403bc8ee24ee0fca60581e754032285926
Tx public key: 4eaa744bf0f979e2eb5417d655ef6b0266211c8beeb4cf87bfd9df5cb8feba09
Timestamp: 1755760358 Timestamp [UCT]: 2025-08-21 07:12:38 Age [y:d:h:m:s]: 00:045:15:44:37
Block: 1351114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32489 RingCT/type: yes/0
Extra: 014eaa744bf0f979e2eb5417d655ef6b0266211c8beeb4cf87bfd9df5cb8feba090211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55a9f2e77317d40d7ebe829390c160a1b0700fb4d69f39da421d4df27ab7d8f5 0.600000000000 1839063 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": 1351124, "vin": [ { "gen": { "height": 1351114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55a9f2e77317d40d7ebe829390c160a1b0700fb4d69f39da421d4df27ab7d8f5" } } ], "extra": [ 1, 78, 170, 116, 75, 240, 249, 121, 226, 235, 84, 23, 214, 85, 239, 107, 2, 102, 33, 28, 139, 238, 180, 207, 135, 191, 217, 223, 92, 184, 254, 186, 9, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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