← previous blocknext block →recent activity
Analyzing
Block #96,019,405
30 transactions · 25 stateful · 2026-08-14 21:02:21 UTC
Parallelism
73/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,019,405 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w28w19w210w311w413w514w618w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9a63764…f004
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0xb967fc94…d7d4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xb9a637644e…f8f004
Audit this contract →
← previous block·next block →recent activity