← previous blocknext block →recent activity
Analyzing
Block #98,672,784
54 transactions · 47 stateful · 2026-08-24 05:15:44 UTC
Parallelism
67/100
Blocked
66%
Avg conflicts / tx
3.22
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #98,672,784 · 54 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w18w29w310w411w514w117w228w229w634w738w141w543w744w847w1151w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
12 touches
15 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
12 touches
15 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