← previous blocknext block →recent activity
Analyzing
Block #90,557,104
12 transactions · 12 stateful · 2026-07-26 18:28:50 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,557,104 · 12 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
3w06w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3f50773b…47ef
0x34b655…2a6f
6 touches
3 conflicts
0x21280422…0930
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity