← previous blocknext block →recent activity
Analyzing
Block #95,085,229
22 transactions · 17 stateful · 2026-08-11 14:28:30 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,085,229 · 22 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
4w05w19w010w212w116w017w318w420w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7f2eca…cf5e
0x34b655…2a6f
8 touches
6 conflicts
0x7b987499…a00c
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xf99d2cfb…dcdb
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0x1c7f2eca4a…e4cf5e
Audit this contract →
← previous block·next block →recent activity