← previous blocknext block →recent activity
Analyzing
Block #99,113,015
40 transactions · 32 stateful · 2026-08-25 18:21:51 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,113,015 · 40 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
1w05w06w18w09w110w011w112w213w314w215w318w424w127w429w234w535w636w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x476d3a0b…579c
0xd32edf…ff58
7 touches
6 conflicts
0x9c168b41…7486
0x34b655…2a6f
6 touches
3 conflicts
0x1625802c…ff96
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity