← previous blocknext block →recent activity
Analyzing
Block #96,339,297
21 transactions · 19 stateful · 2026-08-15 23:51:21 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,339,297 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w210w311w014w215w316w417w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca995928…ded0
0x34b655…2a6f
8 touches
6 conflicts
0xcec993c9…34bf
0x34b655…2a6f
8 touches
6 conflicts
0x235e1426…eb44
0xd32edf…ff58
7 touches
6 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xee8237bd…46ad
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity