Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da539056ac598db2dcb7d29b5f48de54bb57e59aa54576ae0eb32cd3377cbb37

Tx prefix hash: 566d89871b4b46435f55aac552109dffc3ebbd9aab6e116bb3f797d4903b275f
Tx public key: c3b2c4d3c7cdeed28ac51782a523d16883d7456477f6edc0f61ed252198187dc
Timestamp: 1765446541 Timestamp [UCT]: 2025-12-11 09:49:01 Age [y:d:h:m:s]: 00:016:18:17:46
Block: 1431197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12008 RingCT/type: yes/0
Extra: 01c3b2c4d3c7cdeed28ac51782a523d16883d7456477f6edc0f61ed252198187dc021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d53e5904869608d58fdbaa23c81d2dfb0393bd5a74f65b734d427853a38e3b4f 0.600000000000 1919952 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": 1431207, "vin": [ { "gen": { "height": 1431197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53e5904869608d58fdbaa23c81d2dfb0393bd5a74f65b734d427853a38e3b4f" } } ], "extra": [ 1, 195, 178, 196, 211, 199, 205, 238, 210, 138, 197, 23, 130, 165, 35, 209, 104, 131, 215, 69, 100, 119, 246, 237, 192, 246, 30, 210, 82, 25, 129, 135, 220, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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