← previous blocknext block →recent activity
Analyzing
Block #90,546,010
16 transactions · 14 stateful · 2026-07-26 17:33:01 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,546,010 · 16 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
5w06w17w28w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf0bd9219…d498
0x34b655…2a6f
6 touches
3 conflicts
0x1294a92c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity