Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9b0bcec8dde86dadf814bcf2e0c388d9546f7a3763dd1dcf0803b47377d0655

Tx prefix hash: 63401df557c8b338679cadea500ebb3a7b6ce5f11d5c4f4e0af5f7ac03dae07a
Tx public key: d1c7f404cdab90eda2dfbd3cdef2f8751cbed7546e2f27191ef054dfe3e3eda2
Timestamp: 1737821689 Timestamp [UCT]: 2025-01-25 16:14:49 Age [y:d:h:m:s]: 00:330:09:50:29
Block: 1205113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233736 RingCT/type: yes/0
Extra: 01d1c7f404cdab90eda2dfbd3cdef2f8751cbed7546e2f27191ef054dfe3e3eda2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49f0fd8873996aa757def90da2ab81bd0eb3a4c172df13cb1d8754cccf9c2e88 0.600000000000 1691810 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": 1205123, "vin": [ { "gen": { "height": 1205113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49f0fd8873996aa757def90da2ab81bd0eb3a4c172df13cb1d8754cccf9c2e88" } } ], "extra": [ 1, 209, 199, 244, 4, 205, 171, 144, 237, 162, 223, 189, 60, 222, 242, 248, 117, 28, 190, 215, 84, 110, 47, 39, 25, 30, 240, 84, 223, 227, 227, 237, 162, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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