← previous blocknext block →recent activity
Analyzing
Block #95,592,066
14 transactions · 14 stateful · 2026-08-13 09:11:24 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,592,066 · 14 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
1w02w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8e9a7d26…688c
0x34b655…2a6f
6 touches
3 conflicts
0x28095955…1280
0x34b655…2a6f
6 touches
3 conflicts
0xb713decc…ee30
0x34b655…2a6f
6 touches
3 conflicts
0x17935a8f…a796
0x34b655…2a6f
6 touches
3 conflicts
0x2b093939…9085
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity