← previous blocknext block →recent activity
Analyzing
Block #96,798,122
13 transactions · 11 stateful · 2026-08-17 14:19:20 UTC
Parallelism
46/100
Blocked
64%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,798,122 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w08w49w111w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3a5581fb…e85c
0x34b655…2a6f
8 touches
6 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
6 touches
3 conflicts
0xfaa5c672…5681
0x34b655…2a6f
6 touches
3 conflicts
0x523de645…4f58
0x34b655…2a6f
4 touches
1 conflict
0x5d6baa15…7aba
0x34b655…2a6f
4 touches
1 conflict
0x6e1d16c5…2d3e
0x34b655…2a6f
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity