← previous blocknext block →recent activity
Analyzing
Block #90,538,111
9 transactions · 7 stateful · 2026-07-26 16:53:17 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,538,111 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c2c8c1…c2a8
0x34b655…2a6f
6 touches
3 conflicts
0xf8a748aa…446a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x8aea13db…5f7f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xf7376b12…e7b1
0x34b655…2a6f
5 touches
3 conflicts
0x71e39e15…640b
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…6425
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
3 conflicts on slot 0x06c2c8c13e…dfc2a8
Audit this contract →
← previous block·next block →recent activity