← previous blocknext block →recent activity
Analyzing
Block #95,157,078
13 transactions · 9 stateful · 2026-08-11 20:29:55 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,157,078 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcaebe79…9811
0x34b655…2a6f
6 touches
3 conflicts
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
2 touches
0 conflicts
0xee06e767…00d6
0x34b655…2a6f
2 touches
0 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
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
3 conflicts on slot 0xdcaebe79a5…5b9811
Audit this contract →
← previous block·next block →recent activity