Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22fa3393e39250171d244d344487aa9277a2968dfffc8f27d834fea5bb8231d7

Tx prefix hash: 823b215028f39d509abeafd550a7c9abaea517c2f65ce17c2d779d5b2a4a8316
Tx public key: cedeb20b29340b6aca0eaca272b4869c7bdf77a4ed6f087a61c03d15eaa2b19a
Timestamp: 1763971621 Timestamp [UCT]: 2025-11-24 08:07:01 Age [y:d:h:m:s]: 00:046:08:05:39
Block: 1418966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33189 RingCT/type: yes/0
Extra: 01cedeb20b29340b6aca0eaca272b4869c7bdf77a4ed6f087a61c03d15eaa2b19a021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f437efcb34cf1e3699d356944e65c01e5a309359784759a3a02f8551a9d49261 0.600000000000 1907499 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": 1418976, "vin": [ { "gen": { "height": 1418966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f437efcb34cf1e3699d356944e65c01e5a309359784759a3a02f8551a9d49261" } } ], "extra": [ 1, 206, 222, 178, 11, 41, 52, 11, 106, 202, 14, 172, 162, 114, 180, 134, 156, 123, 223, 119, 164, 237, 111, 8, 122, 97, 192, 61, 21, 234, 162, 177, 154, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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