← previous blocknext block →recent activity
Analyzing
Block #95,710,263
15 transactions · 14 stateful · 2026-08-13 19:06:46 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,710,263 · 15 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
1w02w14w08w09w110w211w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59a07ac0…728d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22385bd8…65e4
0x34b655…2a6f
4 touches
1 conflict
0x390dd46c…deef
0x34b655…2a6f
4 touches
1 conflict
0x48212f5b…7f49
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
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 0x59a07ac0ce…5c728d
Audit this contract →
← previous block·next block →recent activity