← previous blocknext block →recent activity
Analyzing
Block #99,134,730
23 transactions · 23 stateful · 2026-08-25 20:11:13 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,134,730 · 23 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
2w03w14w25w06w18w09w012w013w114w115w216w318w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4a05e953…0a1b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0x2202504e…fad0
0x34b655…2a6f
6 touches
3 conflicts
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x34bc92c6…d788
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity