← previous blocknext block →recent activity
Analyzing
Block #95,030,308
23 transactions · 21 stateful · 2026-08-11 09:51:27 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,030,308 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w110w011w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x70005f1b…a377
0x34b655…2a6f
8 touches
6 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
8 touches
6 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
6 touches
3 conflicts
0xa25dc691…44f8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x3a5cd535…3546
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity