← previous blocknext block →recent activity
Analyzing
Block #95,641,822
23 transactions · 21 stateful · 2026-08-13 13:21:40 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,641,822 · 23 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
1w02w13w04w15w28w09w110w211w313w117w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x9408df94…6750
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x100593c2…32ce
0x34b655…2a6f
4 touches
1 conflict
0x2c429f11…0652
0x34b655…2a6f
4 touches
1 conflict
0x3de86e79…4d3d
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity