Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c3e733e1b036fb5e1cc054726dce952f2c2baef1e09881eea5cabccb8f84246

Tx prefix hash: 28936394f602ea52900f8f44788eff244d9a9f97a2f00ada6049c2aa42050b4e
Tx public key: 9064176b0cfda5e7fc704b891ef013a98d2c5316708d7587b7884422999d5567
Timestamp: 1745449420 Timestamp [UCT]: 2025-04-23 23:03:40 Age [y:d:h:m:s]: 00:211:02:30:13
Block: 1268023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148593 RingCT/type: yes/0
Extra: 019064176b0cfda5e7fc704b891ef013a98d2c5316708d7587b7884422999d5567021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a364d345207da1ee6dc9b0848b710ab83c736f11af7794bcf680fb4a3569e5f 0.600000000000 1755252 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": 1268033, "vin": [ { "gen": { "height": 1268023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a364d345207da1ee6dc9b0848b710ab83c736f11af7794bcf680fb4a3569e5f" } } ], "extra": [ 1, 144, 100, 23, 107, 12, 253, 165, 231, 252, 112, 75, 137, 30, 240, 19, 169, 141, 44, 83, 22, 112, 141, 117, 135, 183, 136, 68, 34, 153, 157, 85, 103, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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