← previous blocknext block →recent activity
Analyzing
Block #90,539,362
14 transactions · 14 stateful · 2026-07-26 16:59:35 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,539,362 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w18w29w311w412w5
- 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
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x590f63c9…5df9
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a411
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a412
0x34b655…2a6f
4 touches
1 conflict
0xf0bd9219…d498
0x34b655…2a6f
4 touches
1 conflict
0x43afd8b5…f0c3
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