← previous blocknext block →recent activity
Analyzing
Block #98,838,338
40 transactions · 34 stateful · 2026-08-24 19:13:19 UTC
Parallelism
60/100
Blocked
62%
Avg conflicts / tx
3.3
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,838,338 · 40 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w111w212w314w415w019w522w123w024w125w226w327w428w529w631w732w833w934w1035w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb409e204…89ac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x88ea9cd5…ee68
0x34b655…2a6f
7 touches
6 conflicts
0x10d80fee…dbda
0x2b46c0…1669
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity