← previous blocknext block →recent activity
Analyzing
Block #99,368,312
24 transactions · 23 stateful · 2026-08-26 15:46:41 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,368,312 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w37w411w412w113w217w320w521w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa0c5188…06f2
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x018da3ff…0784
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xded7831c…3c4a
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
15 conflicts on slot 0xfa0c518825…0b06f2
Audit this contract →
← previous block·next block →recent activity