← previous blocknext block →recent activity
Analyzing
Block #95,723,517
17 transactions · 14 stateful · 2026-08-13 20:13:38 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,723,517 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0x0a50c50a…f907
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x2f3561fa…8d5d
0x34b655…2a6f
2 touches
0 conflicts
0x4565f421…80b9
0x34b655…2a6f
2 touches
0 conflicts
0x63ac310a…f307
0x34b655…2a6f
2 touches
0 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xc01decc387…5708a1
Audit this contract →
← previous block·next block →recent activity