Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d63dd090d537a6861f6c9c6a41ae29a160a6cfce9332183b2414a1edfeda60

Tx prefix hash: c9486681c561af619201c658c7cc8fbe608b8efad31013f05c42c1f556a6ab53
Tx public key: 063d7bfa18e2a8f58ecf3849dc915587fe6f5562f4e67907b90d716c0ac2bac5
Timestamp: 1754583435 Timestamp [UCT]: 2025-08-07 16:17:15 Age [y:d:h:m:s]: 00:009:02:34:31
Block: 1342215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5783 RingCT/type: yes/0
Extra: 01063d7bfa18e2a8f58ecf3849dc915587fe6f5562f4e67907b90d716c0ac2bac5021100000012ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4396d1aa179506281f5bf4dfe59e7d6e524ba84f37f79259e2b318bf39ca335e 0.600000000000 1830046 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": 1342225, "vin": [ { "gen": { "height": 1342215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4396d1aa179506281f5bf4dfe59e7d6e524ba84f37f79259e2b318bf39ca335e" } } ], "extra": [ 1, 6, 61, 123, 250, 24, 226, 168, 245, 142, 207, 56, 73, 220, 145, 85, 135, 254, 111, 85, 98, 244, 230, 121, 7, 185, 13, 113, 108, 10, 194, 186, 197, 2, 17, 0, 0, 0, 18, 173, 121, 72, 208, 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