← previous blocknext block →recent activity
Analyzing
Block #94,697,044
16 transactions · 14 stateful · 2026-08-10 05:53:39 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,697,044 · 16 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
1w04w05w16w29w310w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x53699236…fede
0x34b655…2a6f
8 touches
6 conflicts
0xc134ef60…a792
0x34b655…2a6f
6 touches
3 conflicts
0xf0e6cbe4…22de
0x34b655…2a6f
4 touches
1 conflict
0x093ed178…3946
0x34b655…2a6f
4 touches
1 conflict
0x1da820ae…c04a
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity