← previous blocknext block →recent activity
Analyzing
Block #91,062,629
8 transactions · 8 stateful · 2026-07-28 12:52:57 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,062,629 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x8a5a4203…e5c5
0x34b655…2a6f
3 touches
1 conflict
0x299363d4…04d3
0x34b655…2a6f
3 touches
1 conflict
0x1bc07c63…d6ad
0x34b655…2a6f
2 touches
0 conflicts
0x3d22c439…de6d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity