Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0269fbd8cc486d88fb0275d2dcc6a19f6f441adf34637ba045f5954dbe97a551

Tx prefix hash: a8fc24797dae91251ad643ed90ba356de93959cd751cbbd7e0609ac8c7d7318c
Tx public key: 334668df7bf09e2f2a491b6e156be2c5ee7d95c87f8f23a8256a4f11540ea5d3
Timestamp: 1736932568 Timestamp [UCT]: 2025-01-15 09:16:08 Age [y:d:h:m:s]: 00:153:21:52:16
Block: 1197784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109711 RingCT/type: yes/0
Extra: 01334668df7bf09e2f2a491b6e156be2c5ee7d95c87f8f23a8256a4f11540ea5d30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03d678d1b154e84ddd1bd4008ad4c023960a394a86058970ce67fdfd61d73c71 0.600000000000 1684401 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": 1197794, "vin": [ { "gen": { "height": 1197784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03d678d1b154e84ddd1bd4008ad4c023960a394a86058970ce67fdfd61d73c71" } } ], "extra": [ 1, 51, 70, 104, 223, 123, 240, 158, 47, 42, 73, 27, 110, 21, 107, 226, 197, 238, 125, 149, 200, 127, 143, 35, 168, 37, 106, 79, 17, 84, 14, 165, 211, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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