← previous blocknext block →recent activity
Analyzing
Block #95,370,475
30 transactions · 24 stateful · 2026-08-12 14:35:10 UTC
Parallelism
90/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,370,475 · 30 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
1w04w15w08w09w110w111w012w013w116w020w221w123w227w028w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x421099c9…8896
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x0a332311…6e0a3c
1 conflict on slot 0x0ef74796d8…7ccd18
Audit this contract →
← previous block·next block →recent activity