Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf5b6df07be1f4a4a4057ea06a236b64ad8524048a044a09e5e2756188f3629

Tx prefix hash: fe7261f6f8c03dcf6dafabf1e54bf972df43d29f53820eaff1d741eb12330a92
Tx public key: d6480cd5663a016800b4b7e5223d26b3bd34c63d6a706e1c9d2a3cece5bec010
Timestamp: 1751774700 Timestamp [UCT]: 2025-07-06 04:05:00 Age [y:d:h:m:s]: 00:137:07:58:46
Block: 1319686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96533 RingCT/type: yes/0
Extra: 01d6480cd5663a016800b4b7e5223d26b3bd34c63d6a706e1c9d2a3cece5bec01002110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4f0aa4f4e4cf7335440d17d1ba456a2319d2728663852b50d76379cf44a533 0.600000000000 1807379 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": 1319696, "vin": [ { "gen": { "height": 1319686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4f0aa4f4e4cf7335440d17d1ba456a2319d2728663852b50d76379cf44a533" } } ], "extra": [ 1, 214, 72, 12, 213, 102, 58, 1, 104, 0, 180, 183, 229, 34, 61, 38, 179, 189, 52, 198, 61, 106, 112, 110, 28, 157, 42, 60, 236, 229, 190, 192, 16, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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