← previous blocknext block →recent activity
Analyzing
Block #90,042,266
9 transactions · 9 stateful · 2026-07-24 22:59:12 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,042,266 · 9 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
3w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96df3508…ebf5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x1ab86049…60a6
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x3ed31132…62b6
0x34b655…2a6f
2 touches
0 conflicts
0x45ea7a97…bbb3
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 0x96df350841…39ebf5
Audit this contract →
← previous block·next block →recent activity