← previous blocknext block →recent activity
Analyzing
Block #98,605,737
63 transactions · 62 stateful · 2026-08-23 23:26:40 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
2.46
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,605,737 · 63 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w09w110w211w312w013w114w220w322w125w434w135w243w444w246w547w648w757w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfc81faf7…1417
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x627738d1…db02
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity