← previous blocknext block →recent activity
Analyzing
Block #91,403,076
23 transactions · 23 stateful · 2026-07-29 17:26:48 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,403,076 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w09w110w212w313w414w519w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1526b11f…8b21
0x34b655…2a6f
10 touches
10 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x042b4bd1…b4d8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity