← previous blocknext block →recent activity
Analyzing
Block #98,490,001
85 transactions · 64 stateful · 2026-08-23 13:24:36 UTC
Parallelism
81/100
Blocked
69%
Avg conflicts / tx
2.42
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,490,001 · 85 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
1w03w14w05w26w07w18w29w010w314w215w118w020w123w224w330w431w538w848w153w954w1055w1062w11
- 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
14 touches
21 conflicts
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 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