← previous blocknext block →recent activity
Analyzing
Block #90,813,756
18 transactions · 18 stateful · 2026-07-27 16:00:05 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,813,756 · 18 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
1w02w14w06w07w18w19w110w211w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x41377979…0a18
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 0x35b89cd80c…f05092
Audit this contract →
← previous block·next block →recent activity