Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dceecba33edafff9e54762f2414254c6f5e274f030d33df146c061e49cf7bcc

Tx prefix hash: 5809de48e23e2afa4f8dcc09102f6f22d55031c5a9d7162a22f846e7e536f79a
Tx public key: 0674a2524c00a4719c87e7c3e18ed86fb38f448bcfaa4fe8c772d1dfc4d70086
Timestamp: 1751132982 Timestamp [UCT]: 2025-06-28 17:49:42 Age [y:d:h:m:s]: 00:145:02:43:21
Block: 1314679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101792 RingCT/type: yes/0
Extra: 010674a2524c00a4719c87e7c3e18ed86fb38f448bcfaa4fe8c772d1dfc4d70086021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 067768ceba8b2e9d28d2aa72bf9be5efa39c72dc83ac93828181438d65f26ed2 0.600000000000 1802330 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": 1314689, "vin": [ { "gen": { "height": 1314679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "067768ceba8b2e9d28d2aa72bf9be5efa39c72dc83ac93828181438d65f26ed2" } } ], "extra": [ 1, 6, 116, 162, 82, 76, 0, 164, 113, 156, 135, 231, 195, 225, 142, 216, 111, 179, 143, 68, 139, 207, 170, 79, 232, 199, 114, 209, 223, 196, 215, 0, 134, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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