← previous blocknext block →recent activity
Analyzing
Block #95,916,358
14 transactions · 11 stateful · 2026-08-14 12:23:50 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,916,358 · 14 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
1w02w13w24w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xb6864dd7…0df8
0x34b655…2a6f
4 touches
1 conflict
0xd08098a8…f0a6
0x34b655…2a6f
4 touches
1 conflict
0x302f7678…c85e
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity