← previous blocknext block →recent activity
Analyzing
Block #96,213,856
6 transactions · 6 stateful · 2026-08-15 13:20:25 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,213,856 · 6 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x224d6800…4508
0x34b655…2a6f
4 touches
1 conflict
0x003b6142…6bce
0x34b655…2a6f
2 touches
0 conflicts
0x01889594…e1e5
0x34b655…2a6f
2 touches
0 conflicts
0x0c27b92d…451b
0x34b655…2a6f
2 touches
0 conflicts
0x131a4489…c12c
0x34b655…2a6f
2 touches
0 conflicts
0x151e3790…79f3
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity