← previous blocknext block →recent activity
Analyzing
Block #95,113,865
16 transactions · 16 stateful · 2026-08-11 16:52:34 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,113,865 · 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
1w02w13w04w15w27w08w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5985ddc4…eefd
0x34b655…2a6f
6 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0xc82f66db…833d
0x34b655…2a6f
6 touches
3 conflicts
0xf9f9ef49…58f2
0x34b655…2a6f
6 touches
3 conflicts
0xa57576bb…e01f
0x34b655…2a6f
6 touches
3 conflicts
0xfb8e921e…5e90
0x34b655…2a6f
4 touches
1 conflict
0x2ffa0115…ed47
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0x5985ddc465…01eefd
Audit this contract →
← previous block·next block →recent activity