← previous blocknext block →recent activity
Analyzing
Block #95,758,653
23 transactions · 20 stateful · 2026-08-13 23:10:20 UTC
Parallelism
78/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,758,653 · 23 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
2w03w17w010w112w013w119w220w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf9429f9d…a5df
0x40c49f…2af0
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x44b80fe8…bfa7
0x34b655…2a6f
4 touches
1 conflict
0x4b67fb18…a176
0x34b655…2a6f
4 touches
1 conflict
0x50e39ab9…dcf4
0x34b655…2a6f
4 touches
1 conflict
0x97e2bfcd…fb19
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity