← previous blocknext block →recent activity
Analyzing
Block #99,620,034
20 transactions · 18 stateful · 2026-08-27 13:00:24 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,620,034 · 20 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
3w04w17w08w19w212w316w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727f9346…28d8
0x34b655…2a6f
6 touches
3 conflicts
0x39ccd26a…4654
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2caeb7f5…b6bb
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x727f93469d…f128d8
Audit this contract →
← previous block·next block →recent activity