← previous blocknext block →recent activity
Analyzing
Block #99,866,913
21 transactions · 20 stateful · 2026-08-28 09:49:49 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,866,913 · 21 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
1w02w15w07w18w29w313w415w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe62f713c…246f
0x34b655…2a6f
10 touches
10 conflicts
0x2833f8ab…7f95
0x34b655…2a6f
10 touches
10 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
10 touches
10 conflicts
0xef048f92…572b
0x34b655…2a6f
8 touches
6 conflicts
0x4f82ea31…32f4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
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
10 conflicts on slot 0xe62f713c50…8b246f
Audit this contract →
← previous block·next block →recent activity