← previous blocknext block →recent activity
Analyzing
Block #96,561,257
24 transactions · 24 stateful · 2026-08-16 18:27:59 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,561,257 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w08w19w210w311w414w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
14 touches
21 conflicts
0x972e38eb…dc76
0x34b655…2a6f
8 touches
6 conflicts
0x461455a7…0c70
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x9a9e2858…a685
0x34b655…2a6f
6 touches
3 conflicts
0x2d58a69f…6820
0x34b655…2a6f
6 touches
3 conflicts
0x8861b270…e0cb
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
21 conflicts on slot 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity