← previous blocknext block →recent activity
Analyzing
Block #99,456,049
19 transactions · 17 stateful · 2026-08-26 23:08:26 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,456,049 · 19 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
1w03w15w09w111w212w013w314w415w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0x41f621e0…9e98
0x34b655…2a6f
8 touches
6 conflicts
0x0490581d…adaf
0x34b655…2a6f
6 touches
3 conflicts
0x3b56f79b…310f
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity