← previous blocknext block →recent activity
Analyzing
Block #94,058,049
22 transactions · 21 stateful · 2026-08-08 00:03:51 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,058,049 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w211w012w113w214w315w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x501b08c7…f471
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Perpl
6 conflicts on slot 0x501b08c77e…c9f471
Audit this contract →
← previous block·next block →recent activity