Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 568c800fdebb77a6c97a075404befd36c66555efac4eda1becaa3d93f4296e9f

Tx prefix hash: dc07ad11e0d17666374276c2cd0178762a25ccc01808f8794fd979c9c2df9e66
Tx public key: ee17f4761eddfde59219c956d90e4f94e9be6453b4278a90796dd5b364b4147f
Timestamp: 1746526622 Timestamp [UCT]: 2025-05-06 10:17:02 Age [y:d:h:m:s]: 00:269:18:00:02
Block: 1276946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190422 RingCT/type: yes/0
Extra: 01ee17f4761eddfde59219c956d90e4f94e9be6453b4278a90796dd5b364b4147f0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e087ceff918b77df9efbc5197eaaf9c680d829e6a9e51b07719328b502c4e76e 0.600000000000 1764297 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": 1276956, "vin": [ { "gen": { "height": 1276946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e087ceff918b77df9efbc5197eaaf9c680d829e6a9e51b07719328b502c4e76e" } } ], "extra": [ 1, 238, 23, 244, 118, 30, 221, 253, 229, 146, 25, 201, 86, 217, 14, 79, 148, 233, 190, 100, 83, 180, 39, 138, 144, 121, 109, 213, 179, 100, 180, 20, 127, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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