← previous blocknext block →recent activity
Analyzing
Block #91,064,588
16 transactions · 16 stateful · 2026-07-28 13:02:48 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,064,588 · 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
1w02w13w24w16w37w210w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0f898335…7a89
0x34b655…2a6f
6 touches
3 conflicts
0xa735578c…33f5
0x34b655…2a6f
6 touches
3 conflicts
0xf0058e3d…8d7b
0x34b655…2a6f
6 touches
3 conflicts
0xa8dad04b…f666
0x34b655…2a6f
6 touches
3 conflicts
0xfd5be853…17a0
0x34b655…2a6f
6 touches
3 conflicts
0x1c1cd830…ec32
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity