← previous blocknext block →recent activity
Analyzing
Block #90,557,628
11 transactions · 10 stateful · 2026-07-26 18:31:28 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,557,628 · 11 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
4w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x088adada…2aa2
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x2894b5dd…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
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 0x088adada6a…bd2aa2
Audit this contract →
← previous block·next block →recent activity