Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20d280467fa5dbfc2fb9a7fa7559c5214b78793ad5f6ac00f6ab88d2b3787a5

Tx prefix hash: eab48825032b28084922102a878ce1fa798a49a577fb9173c5e6c88c1c893b0b
Tx public key: 8ff1dd34e11d31dcf49593c531025bcb9c2d9b58e474673d62a71b9e4a89924f
Timestamp: 1765136173 Timestamp [UCT]: 2025-12-07 19:36:13 Age [y:d:h:m:s]: 00:015:17:13:44
Block: 1428624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11244 RingCT/type: yes/0
Extra: 018ff1dd34e11d31dcf49593c531025bcb9c2d9b58e474673d62a71b9e4a89924f021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc0df8e67bf69add69b3eda2c15bfe86839e6e83e1d60c1147181bbf18f4cab 0.600000000000 1917343 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": 1428634, "vin": [ { "gen": { "height": 1428624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc0df8e67bf69add69b3eda2c15bfe86839e6e83e1d60c1147181bbf18f4cab" } } ], "extra": [ 1, 143, 241, 221, 52, 225, 29, 49, 220, 244, 149, 147, 197, 49, 2, 91, 203, 156, 45, 155, 88, 228, 116, 103, 61, 98, 167, 27, 158, 74, 137, 146, 79, 2, 17, 0, 0, 0, 1, 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