← previous blocknext block →recent activity
Analyzing
Block #90,291,634
20 transactions · 19 stateful · 2026-07-25 19:59:45 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,291,634 · 20 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
3w04w15w26w38w413w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0x70664c87…57b6
0x34b655…2a6f
6 touches
3 conflicts
0x60c4435a…22cb
0x34b655…2a6f
4 touches
1 conflict
0x7f7bbb0d…6f60
0x34b655…2a6f
4 touches
1 conflict
0x90d127f4…5c92
0x34b655…2a6f
4 touches
1 conflict
0x90d127f4…5c93
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity