← previous blocknext block →recent activity
Analyzing
Block #99,369,104
18 transactions · 14 stateful · 2026-08-26 15:50:40 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,369,104 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w09w010w111w213w214w316w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8906758…2ece
0x34b655…2a6f
8 touches
6 conflicts
0x523de645…4f58
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xde8c16a5…cc15
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
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
6 conflicts on slot 0xf890675816…622ece
Audit this contract →
← previous block·next block →recent activity