← previous blocknext block →recent activity
Analyzing
Block #90,286,909
11 transactions · 10 stateful · 2026-07-25 19:35:45 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,286,909 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x2ed336a4…72b1
0x34b655…2a6f
4 touches
1 conflict
0x1f02c5ca…02d7
0x34b655…2a6f
4 touches
1 conflict
0x6d5aa39a…20b8
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0x277db0e0…0eac
0x065c9d…c394
2 touches
0 conflicts
0xe7f13ea4…a995
0x065c9d…c394
2 touches
0 conflicts
0xf6a46c26…1a68
0x065c9d…c394
2 touches
0 conflicts
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity