← previous blocknext block →recent activity
Analyzing
Block #90,024,879
11 transactions · 9 stateful · 2026-07-24 21:31:36 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,024,879 · 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
5w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04c1c529…0ee1
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x02d895f0…2b93
0x34b655…2a6f
2 touches
0 conflicts
0x0402e15a…d73f
0x34b655…2a6f
2 touches
0 conflicts
0x06e7dbbc…f5b8
0x34b655…2a6f
2 touches
0 conflicts
0x080ca4e8…d573
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 0x04c1c52913…7f0ee1
Audit this contract →
← previous block·next block →recent activity