← previous blocknext block →recent activity
Analyzing
Block #91,276,625
13 transactions · 12 stateful · 2026-07-29 06:50:22 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,276,625 · 13 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
1w02w14w15w27w38w49w411w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd12b6c…02cc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x24933e74…db08
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5c79a7db…b7aa
0x34b655…2a6f
4 touches
1 conflict
0x6e83a321…33a2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x2fd12b6c73…8702cc
Audit this contract →
← previous block·next block →recent activity