← previous blocknext block →recent activity
Analyzing
Block #98,102,067
35 transactions · 31 stateful · 2026-08-22 04:51:48 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,102,067 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w011w012w113w014w115w218w221w023w124w025w128w330w431w532w633w734w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd9b50cd5…b4b1
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
6 touches
3 conflicts
0xc3935765…a58e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x827e7bbd…45bb
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity