Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbc9293afc259d6f81de6cb5b42a0bf40e41e7550b000ced1cc9d56f02ac6fa

Tx prefix hash: 83fe34438bb737b3ab40582666d0b9b4da62099bf8e38b5dbfc158241b4c2f04
Tx public key: 9ecb723642ccfd6c3d8cf888e461006e9798f40c4091ac2f9a302ff86de1c159
Timestamp: 1750778956 Timestamp [UCT]: 2025-06-24 15:29:16 Age [y:d:h:m:s]: 00:150:01:28:25
Block: 1311902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105177 RingCT/type: yes/0
Extra: 019ecb723642ccfd6c3d8cf888e461006e9798f40c4091ac2f9a302ff86de1c159021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7acd7dc698185a1a437d7cddf32ed7ec3e08c8c0e660bc0bdb5e83bf0463d36b 0.600000000000 1799531 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": 1311912, "vin": [ { "gen": { "height": 1311902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7acd7dc698185a1a437d7cddf32ed7ec3e08c8c0e660bc0bdb5e83bf0463d36b" } } ], "extra": [ 1, 158, 203, 114, 54, 66, 204, 253, 108, 61, 140, 248, 136, 228, 97, 0, 110, 151, 152, 244, 12, 64, 145, 172, 47, 154, 48, 47, 248, 109, 225, 193, 89, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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