← previous blocknext block →recent activity
Analyzing
Block #92,286,982
20 transactions · 20 stateful · 2026-08-01 19:34:16 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,286,982 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf6e8e884…ad85
0x34b655…2a6f
10 touches
10 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
10 touches
10 conflicts
0xc8304415…4f91
0x34b655…2a6f
8 touches
6 conflicts
0x682345eb…aef0
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0x22b9193d…d40d
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity