← previous blocknext block →recent activity
Analyzing
Block #95,203,768
11 transactions · 11 stateful · 2026-08-12 00:24:45 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,203,768 · 11 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
2w03w04w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
6 touches
3 conflicts
0xd0dfd824…79a6
0x34b655…2a6f
6 touches
3 conflicts
0x330df1e6…7586
0x34b655…2a6f
4 touches
1 conflict
0xbd9491f7…dd92
0x34b655…2a6f
4 touches
1 conflict
0x3a823597…b343
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad7
0x34b655…2a6f
4 touches
1 conflict
0x330df1e6…7587
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 0xbe9baf16a9…e6df37
Audit this contract →
← previous block·next block →recent activity