← previous blocknext block →recent activity
Analyzing
Block #99,444,266
20 transactions · 16 stateful · 2026-08-26 22:09:06 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,444,266 · 20 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
2w03w14w28w19w210w311w415w517w419w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
12 touches
15 conflicts
0x676207a8…5d7e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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 0x2202504ef1…9ffad0
Audit this contract →
← previous block·next block →recent activity