← previous blocknext block →recent activity
Analyzing
Block #95,163,420
13 transactions · 12 stateful · 2026-08-11 21:01:49 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,163,420 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w28w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4268cc8…dc39
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x5e0bf019…75fd
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9c1ae785…602e
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 0xf4268cc8b9…24dc39
Audit this contract →
← previous block·next block →recent activity