Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d68254f1e6601a2aaef694988c4b23ee34afdd388f434f2f0ecff93c64978d7

Tx prefix hash: 4c4db22d851545835145a202aca094bc7ded9d5c4ea58a8f8c6c2345ee8ebb79
Tx public key: 7b45c4a1d8e2ecf7ef23d7df06830efbb3510890d09791defbb285e36bb0be2f
Timestamp: 1757836421 Timestamp [UCT]: 2025-09-14 07:53:41 Age [y:d:h:m:s]: 00:061:02:22:38
Block: 1368129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43751 RingCT/type: yes/0
Extra: 017b45c4a1d8e2ecf7ef23d7df06830efbb3510890d09791defbb285e36bb0be2f021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeb990feb621b598d970aab57ecfd99e916abe7ee9e6f176f186718001df8bb7 0.600000000000 1856172 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": 1368139, "vin": [ { "gen": { "height": 1368129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeb990feb621b598d970aab57ecfd99e916abe7ee9e6f176f186718001df8bb7" } } ], "extra": [ 1, 123, 69, 196, 161, 216, 226, 236, 247, 239, 35, 215, 223, 6, 131, 14, 251, 179, 81, 8, 144, 208, 151, 145, 222, 251, 178, 133, 227, 107, 176, 190, 47, 2, 17, 0, 0, 0, 4, 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