← previous blocknext block →recent activity
Analyzing
Block #95,479,971
13 transactions · 13 stateful · 2026-08-12 23:47:36 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,479,971 · 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
2w03w14w06w07w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0xf96c955b…06e8
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x4b80417b…75c3
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x6aef82db…28d6
0x34b655…2a6f
4 touches
1 conflict
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity