← previous blocknext block →recent activity
Analyzing
Block #90,240,175
20 transactions · 19 stateful · 2026-07-25 15:39:40 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,240,175 · 20 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
1w02w13w04w16w07w19w210w011w213w314w415w016w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe44c4fc1…43b1
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x0c3f0c86…e1b5
0xd32edf…ff58
5 touches
3 conflicts
0xd3d2b624…594f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xe44c4fc146…f643b1
Audit this contract →
← previous block·next block →recent activity