← previous blocknext block →recent activity
Analyzing
Block #96,652,267
13 transactions · 13 stateful · 2026-08-17 02:05:45 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,652,267 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ce18f62…c25a
0x34b655…2a6f
8 touches
6 conflicts
0x19cbeea8…ecf3
0x34b655…2a6f
6 touches
3 conflicts
0x7ba55bb3…0191
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xbe9062cc…0c24
0x34b655…2a6f
4 touches
1 conflict
0x4cb2d1c8…e491
0x34b655…2a6f
4 touches
1 conflict
0xf78695bc…b542
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 0x0ce18f62c6…60c25a
Audit this contract →
← previous block·next block →recent activity