Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c95317407c74f3dadaf11c2e8744ce0778fc304912fd950e1f407c06f428e24f

Tx prefix hash: 4fa093bbc38758426d1b589e21ba26ec3a110b1798a8ee2c4c5a64b18cd6c3b5
Tx public key: dce8d68f39cbe13d360adc72ab07b82f4dc5f02a7566ae7c1252ecef0cad440b
Timestamp: 1749363016 Timestamp [UCT]: 2025-06-08 06:10:16 Age [y:d:h:m:s]: 00:155:18:33:34
Block: 1300444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109002 RingCT/type: yes/0
Extra: 01dce8d68f39cbe13d360adc72ab07b82f4dc5f02a7566ae7c1252ecef0cad440b021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f78c9ac89ad35c9cf36170d5063465ccf2e7155ef45e3a905b23935a01acdf26 0.600000000000 1787993 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": 1300454, "vin": [ { "gen": { "height": 1300444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f78c9ac89ad35c9cf36170d5063465ccf2e7155ef45e3a905b23935a01acdf26" } } ], "extra": [ 1, 220, 232, 214, 143, 57, 203, 225, 61, 54, 10, 220, 114, 171, 7, 184, 47, 77, 197, 240, 42, 117, 102, 174, 124, 18, 82, 236, 239, 12, 173, 68, 11, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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