← previous blocknext block →recent activity
Analyzing
Block #96,258,707
10 transactions · 9 stateful · 2026-08-15 17:06:01 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,258,707 · 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
5w06w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x0eaa3f4e…2992
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xca0fce55…8baa
0x34b655…2a6f
4 touches
1 conflict
0x081e86ec…551c
0x34b655…2a6f
2 touches
0 conflicts
0x1c97ceaf…d70a
0x34b655…2a6f
2 touches
0 conflicts
0x1ec64c44…6909
0x34b655…2a6f
2 touches
0 conflicts
0x29c1a140…099f
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 0x2aab08973a…f178f7
Audit this contract →
← previous block·next block →recent activity