← previous blocknext block →recent activity

Analyzing

Block #95,854,056

20 transactions · 17 stateful · 2026-08-14 07:10:12 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,854,056  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0x3820895c…ae90

0x065c9d…c394

6 touches
3 conflicts

0xa8536d3b…0538

0x065c9d…c394

6 touches
3 conflicts

0xef05b756…d18f

0x851145…3f07

4 touches
1 conflict

0x595233b5…c4aa

0x754704…b603

4 touches
1 conflict

0x6e7bb7b2…df82

0x754704…b603

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: USDC (USDC)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity