← previous blocknext block →recent activity
Analyzing
Block #96,524,999
12 transactions · 9 stateful · 2026-08-16 15:25:38 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,524,999 · 12 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
1w02w13w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf2476c…859d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0x3fcf8849…ee1d
0x34b655…2a6f
2 touches
0 conflicts
0x4f44533d…c3a0
0x34b655…2a6f
2 touches
0 conflicts
0x6819f434…82c8
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 0xbaf2476c1f…f0859d
Audit this contract →
← previous block·next block →recent activity