← previous blocknext block →recent activity
Analyzing
Block #99,157,481
18 transactions · 17 stateful · 2026-08-25 22:05:40 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,157,481 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w18w210w011w012w113w214w115w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc69f5267…4857
0x8964d7…10f8
6 touches
3 conflicts
0xc69f5267…485b
0x8964d7…10f8
6 touches
3 conflicts
0xc69f5267…485c
0x8964d7…10f8
6 touches
3 conflicts
0xc69f5267…485d
0x8964d7…10f8
6 touches
3 conflicts
0xcfd3d54d…9263
0x8964d7…10f8
6 touches
3 conflicts
0xcfd3d54d…9264
0x8964d7…10f8
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xc69f5267…4858
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xc69f5267ce…ad4857
Audit this contract →
← previous block·next block →recent activity