← previous blocknext block →recent activity
Analyzing
Block #95,388,261
25 transactions · 21 stateful · 2026-08-12 16:05:15 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,388,261 · 25 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
1w02w03w14w08w09w110w011w114w216w117w219w020w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd51eb25…31f9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc85f42b6…6f23
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 0xcd51eb2512…2431f9
Audit this contract →
← previous block·next block →recent activity