← previous blocknext block →recent activity
Analyzing
Block #96,784,099
16 transactions · 15 stateful · 2026-08-17 13:08:48 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,784,099 · 16 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
4w05w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb018712d…66f6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x08156667…3a59
0x34b655…2a6f
2 touches
0 conflicts
0x1d6f1dad…7ae3
0x34b655…2a6f
2 touches
0 conflicts
0x2de9863d…96dc
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 0xb018712d0b…9366f6
Audit this contract →
← previous block·next block →recent activity