← previous blocknext block →recent activity
Analyzing
Block #96,580,750
58 transactions · 55 stateful · 2026-08-16 20:06:01 UTC
Parallelism
97/100
Blocked
4%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,580,750 · 58 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
2w055w156w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x500df02b…3458
0x34b655…2a6f
2 touches
0 conflicts
0x513b0c80…d2d9
0x34b655…2a6f
2 touches
0 conflicts
0x6100f5dd…6a7f
0x34b655…2a6f
2 touches
0 conflicts
0xf63c2a2b…bc5f
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 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity