← previous blocknext block →recent activity
Analyzing
Block #91,138,323
25 transactions · 23 stateful · 2026-07-28 19:13:48 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,138,323 · 25 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
1w04w06w17w08w110w011w212w114w115w216w017w118w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0x3307aebb…fe62
0x34b655…2a6f
6 touches
3 conflicts
0x4694689f…f238
0x34b655…2a6f
6 touches
3 conflicts
0x6e83a321…33a2
0x34b655…2a6f
6 touches
3 conflicts
0x8047e9b2…9bb8
0x34b655…2a6f
6 touches
3 conflicts
0xdb9ee593…17d1
0xd32edf…ff58
5 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