← previous blocknext block →recent activity
Analyzing
Block #99,200,782
24 transactions · 22 stateful · 2026-08-26 01:43:31 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,200,782 · 24 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
2w03w16w19w010w112w216w018w021w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0x8d42e816…cb67
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity