Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd412d67a7f2c8ce5c5c06e44530022ef32a41764af2fe04307fd18b98a3e008

Tx prefix hash: 8dccc991ced3054744c3ee78bf4e26fa74c750c7870d1f4cbcb268886cdc105a
Tx public key: a8ffec919e156744a55a893cebec88fb18693521de23b9ecfb5e2ee66cb33c91
Timestamp: 1751190309 Timestamp [UCT]: 2025-06-29 09:45:09 Age [y:d:h:m:s]: 00:142:13:26:25
Block: 1315123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100001 RingCT/type: yes/0
Extra: 01a8ffec919e156744a55a893cebec88fb18693521de23b9ecfb5e2ee66cb33c91021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f218e3f0f7c9f49864f247626ae2a04b3999e1ca927d639e73b507e28352657 0.600000000000 1802776 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": 1315133, "vin": [ { "gen": { "height": 1315123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f218e3f0f7c9f49864f247626ae2a04b3999e1ca927d639e73b507e28352657" } } ], "extra": [ 1, 168, 255, 236, 145, 158, 21, 103, 68, 165, 90, 137, 60, 235, 236, 136, 251, 24, 105, 53, 33, 222, 35, 185, 236, 251, 94, 46, 230, 108, 179, 60, 145, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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