← previous blocknext block →recent activity
Analyzing
Block #92,538,925
25 transactions · 22 stateful · 2026-08-02 16:41:20 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,538,925 · 25 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
1w02w13w04w16w07w09w110w212w321w022w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x881782b6…c51a
0x34b655…2a6f
6 touches
3 conflicts
0x1e737223…2278
0x34b655…2a6f
6 touches
3 conflicts
0xd744c84a…50b5
0x34b655…2a6f
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x4e742f0d…c696
0x34b655…2a6f
4 touches
1 conflict
0x65487580…b5eb
0x34b655…2a6f
4 touches
1 conflict
0x68a1d6b3…fb6f
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
3 conflicts on slot 0x881782b64f…84c51a
Audit this contract →
← previous block·next block →recent activity