← previous blocknext block →recent activity
Analyzing
Block #90,433,284
10 transactions · 9 stateful · 2026-07-26 08:04:59 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,433,284 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72f56d01…046b
0x34b655…2a6f
4 touches
1 conflict
0xca0fce55…8baa
0x34b655…2a6f
4 touches
1 conflict
0xeea96826…b11e
0x34b655…2a6f
4 touches
1 conflict
0xf28ee159…1f3b
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8f791153…4f53
0x34b655…2a6f
4 touches
1 conflict
0xf2d8abfb…9cb6
0x34b655…2a6f
2 touches
0 conflicts
0xf85fbefc…6825
0x34b655…2a6f
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
1 conflict on slot 0x72f56d0114…85046b
Audit this contract →
← previous block·next block →recent activity