Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566fb5e7705fb6ea00eabd0525fb549a7cd73dd62683a3de69d3c928e32a3cd2

Tx prefix hash: 13de8ec5241cc0a438be716cf3024284187625cc03114179a9f42b5f911136f8
Tx public key: d6292ef9d3e253959ee0270577b7e662760af3bf97ab3e00e533e3e12b71feb2
Timestamp: 1736904289 Timestamp [UCT]: 2025-01-15 01:24:49 Age [y:d:h:m:s]: 00:153:11:05:41
Block: 1197547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109408 RingCT/type: yes/0
Extra: 01d6292ef9d3e253959ee0270577b7e662760af3bf97ab3e00e533e3e12b71feb2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df6a9995926d2ed24053ed05486c503b3ce4fdf045f2bd9b755f0aeddaccd6f7 0.600000000000 1684158 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": 1197557, "vin": [ { "gen": { "height": 1197547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df6a9995926d2ed24053ed05486c503b3ce4fdf045f2bd9b755f0aeddaccd6f7" } } ], "extra": [ 1, 214, 41, 46, 249, 211, 226, 83, 149, 158, 224, 39, 5, 119, 183, 230, 98, 118, 10, 243, 191, 151, 171, 62, 0, 229, 51, 227, 225, 43, 113, 254, 178, 2, 17, 0, 0, 0, 3, 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