← previous blocknext block →recent activity
Analyzing
Block #90,808,889
13 transactions · 13 stateful · 2026-07-27 15:35:31 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,808,889 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x21771173…f8b0
0x34b655…2a6f
2 touches
0 conflicts
0x22cb88f1…393e
0x34b655…2a6f
2 touches
0 conflicts
0x2a1a17d1…82c0
0x34b655…2a6f
2 touches
0 conflicts
0x2a21b53a…211b
0x34b655…2a6f
2 touches
0 conflicts
0x31152b1f…e76a
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity