← previous blocknext block →recent activity
Analyzing
Block #91,406,220
20 transactions · 17 stateful · 2026-07-29 17:42:43 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,406,220 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w09w110w213w314w115w218w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd4acc996…b47c
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xc659be24…fe06
0xd32edf…ff58
3 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 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
3 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity