← previous blocknext block →recent activity
Analyzing
Block #91,088,020
24 transactions · 19 stateful · 2026-07-28 15:00:44 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,088,020 · 24 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
1w02w13w08w09w110w211w312w113w314w315w117w218w421w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x75ab7c35…0913
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x83762542…18ed
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity