← previous blocknext block →recent activity
Analyzing
Block #99,870,338
26 transactions · 18 stateful · 2026-08-28 10:07:03 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,870,338 · 26 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
5w07w08w19w110w011w112w113w115w217w321w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffd91f4b…303d
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf0104690…7c3a
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
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
3 conflicts on slot 0xffd91f4b80…70303d
Audit this contract →
← previous block·next block →recent activity