← previous blocknext block →recent activity
Analyzing
Block #96,261,327
10 transactions · 9 stateful · 2026-08-15 17:19:12 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,261,327 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd121f3a2…4df5
0x34b655…2a6f
4 touches
1 conflict
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0x2ffa0115…ed47
0x34b655…2a6f
2 touches
0 conflicts
0x34ac5036…bedf
0x34b655…2a6f
2 touches
0 conflicts
0x6100f5dd…6a7f
0x34b655…2a6f
2 touches
0 conflicts
0x7c86c81a…ca46
0x34b655…2a6f
2 touches
0 conflicts
0x9e599b87…c270
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity