← previous blocknext block →recent activity
Analyzing
Block #95,086,312
10 transactions · 10 stateful · 2026-08-11 14:33:57 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,086,312 · 10 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0140fbd3…d957
0x34b655…2a6f
4 touches
1 conflict
0x15c22181…1354
0x34b655…2a6f
4 touches
1 conflict
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x1adc8ee7…f3ca
0x34b655…2a6f
2 touches
0 conflicts
0x1e0f627b…4ae8
0x34b655…2a6f
2 touches
0 conflicts
0x251e4ed8…a3f4
0x34b655…2a6f
2 touches
0 conflicts
0x25420194…c8b0
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity