← previous blocknext block →recent activity
Analyzing
Block #96,030,254
13 transactions · 12 stateful · 2026-08-14 21:56:54 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,030,254 · 13 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
4w06w08w19w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fb89e5…b3c8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xd29144b1…30b5
0x34b655…2a6f
4 touches
1 conflict
0xde9abc50…930e
0x34b655…2a6f
4 touches
1 conflict
0xb6b61477…ed3e
0x34b655…2a6f
4 touches
1 conflict
0x5f689f7f…d18e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xb7fb89e532…02b3c8
Audit this contract →
← previous block·next block →recent activity