← previous blocknext block →recent activity
Analyzing
Block #95,204,920
16 transactions · 13 stateful · 2026-08-12 00:30:33 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,204,920 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w39w010w111w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa779293b…5e59
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x35563c03…7689
0x34b655…2a6f
6 touches
3 conflicts
0xb90ee587…390a
0x40c49f…2af0
5 touches
3 conflicts
0x4d5053d1…3b7d
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity