Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07900526117b573be91ee21d30f17f54a6728779a7a9beed2a2d550cbc86eabb

Tx prefix hash: d38090f7e37d7ed21bee4d894a9e982562bc920aa937b039c87d111fd0272efe
Tx public key: c11deb5834a2681e0d414a929e2e516acaf5d508166b9fc97e53e2e4f8d129c8
Timestamp: 1767132319 Timestamp [UCT]: 2025-12-30 22:05:19 Age [y:d:h:m:s]: 00:009:10:21:34
Block: 1445155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6773 RingCT/type: yes/0
Extra: 01c11deb5834a2681e0d414a929e2e516acaf5d508166b9fc97e53e2e4f8d129c8021100000003215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea18167bf5fa0bbc77df4713361fbac57d8ec145ec98ba32302ccb0f99134aa4 0.600000000000 1934095 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": 1445165, "vin": [ { "gen": { "height": 1445155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea18167bf5fa0bbc77df4713361fbac57d8ec145ec98ba32302ccb0f99134aa4" } } ], "extra": [ 1, 193, 29, 235, 88, 52, 162, 104, 30, 13, 65, 74, 146, 158, 46, 81, 106, 202, 245, 213, 8, 22, 107, 159, 201, 126, 83, 226, 228, 248, 209, 41, 200, 2, 17, 0, 0, 0, 3, 33, 91, 191, 137, 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