← previous blocknext block →recent activity
Analyzing
Block #98,940,515
36 transactions · 31 stateful · 2026-08-25 03:47:20 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
2.64
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,940,515 · 36 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
1w02w13w27w09w111w012w313w414w515w120w122w325w327w728w829w931w1133w1334w1435w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0x5f5c82f8…079f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity