← previous blocknext block →recent activity
Analyzing
Block #96,784,212
16 transactions · 14 stateful · 2026-08-17 13:09:22 UTC
Parallelism
38/100
Blocked
64%
Avg conflicts / tx
2.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,784,212 · 16 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w59w611w712w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x4efae872…6aa8
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4abfb389…18f4
0x34b655…2a6f
10 touches
10 conflicts
0x28931d3a…8306
0x34b655…2a6f
8 touches
6 conflicts
0xe4f5cdcb…d942
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity