← previous blocknext block →recent activity
Analyzing
Block #91,955,323
18 transactions · 16 stateful · 2026-07-31 15:46:14 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,955,323 · 18 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
1w02w16w27w38w49w413w514w615w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a9274d…78d7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x2362b8af…c01d
0x34b655…2a6f
6 touches
3 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0x8f985aa6…5f12
0x34b655…2a6f
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
10 conflicts on slot 0xe5a9274d87…0678d7
Audit this contract →
← previous block·next block →recent activity