← previous blocknext block →recent activity
Analyzing
Block #99,112,342
23 transactions · 21 stateful · 2026-08-25 18:18:28 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,112,342 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w210w111w216w317w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x89fee327…83c4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x676207a8…5d7e
0x34b655…2a6f
6 touches
3 conflicts
0xa8ab918c…8c14
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity