Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a2e0c38eda22a28a55bcb900e3ce83e88a6e4d54fbcd99e18888dd79121686a

Tx prefix hash: e92a2bf5ff887a8e1b81d7bf34d5ac3087b6b94b6f1c9af275e5e59fed4b7f7a
Tx public key: c64bf7edea074f3f023f5f0c0da6e8a86c9fc618b8b60e9b6de94b77b966913e
Timestamp: 1735813105 Timestamp [UCT]: 2025-01-02 10:18:25 Age [y:d:h:m:s]: 00:096:11:00:05
Block: 1188523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68717 RingCT/type: yes/0
Extra: 01c64bf7edea074f3f023f5f0c0da6e8a86c9fc618b8b60e9b6de94b77b966913e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 403dcb9070164eb16648b90a8d6fb2167632166b8876f490de83021ec8f45704 0.600000000000 1675024 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": 1188533, "vin": [ { "gen": { "height": 1188523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "403dcb9070164eb16648b90a8d6fb2167632166b8876f490de83021ec8f45704" } } ], "extra": [ 1, 198, 75, 247, 237, 234, 7, 79, 63, 2, 63, 95, 12, 13, 166, 232, 168, 108, 159, 198, 24, 184, 182, 14, 155, 109, 233, 75, 119, 185, 102, 145, 62, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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