← previous blocknext block →recent activity
Analyzing
Block #99,589,604
22 transactions · 22 stateful · 2026-08-27 10:23:49 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
2.14
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,589,604 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w19w210w312w416w517w618w720w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x53c41998…7d52
0x34b655…2a6f
6 touches
3 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
6 touches
3 conflicts
0xbbc4bdf7…c62f
0x34b655…2a6f
6 touches
3 conflicts
0xd1bdfcc3…daa5
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity