Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e098457ae997a87e7d5970d2fab1bbb03c5c9409fb0037c1c385748f9c6d5e39

Tx prefix hash: 30cd120df3b262c53dfdbb5d800c8696993f2b976fe2d5244e174731f6b65451
Tx public key: 9fac1e02299194a0c5bfa100751b2abfbcf5298eab74989b259555372f89a9a8
Timestamp: 1745658200 Timestamp [UCT]: 2025-04-26 09:03:20 Age [y:d:h:m:s]: 00:202:15:14:24
Block: 1269764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142533 RingCT/type: yes/0
Extra: 019fac1e02299194a0c5bfa100751b2abfbcf5298eab74989b259555372f89a9a80211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a79313c16efc42eb79b2b1c855326377f2f264ec53900344f17419035cab4371 0.600000000000 1757003 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": 1269774, "vin": [ { "gen": { "height": 1269764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a79313c16efc42eb79b2b1c855326377f2f264ec53900344f17419035cab4371" } } ], "extra": [ 1, 159, 172, 30, 2, 41, 145, 148, 160, 197, 191, 161, 0, 117, 27, 42, 191, 188, 245, 41, 142, 171, 116, 152, 155, 37, 149, 85, 55, 47, 137, 169, 168, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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