← previous blocknext block →recent activity
Analyzing
Block #91,442,943
20 transactions · 17 stateful · 2026-07-29 20:48:34 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,442,943 · 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
4w05w18w09w110w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
10 touches
10 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x10797f0b…439a
0x34b655…2a6f
6 touches
3 conflicts
0x32646adf…e05d
0x34b655…2a6f
6 touches
3 conflicts
0xe00a10fa…79a9
0x34b655…2a6f
6 touches
3 conflicts
0x0b34a794…400b
0x34b655…2a6f
6 touches
3 conflicts
0x0d6d262c…958d
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity