← previous blocknext block →recent activity
Analyzing
Block #98,774,982
68 transactions · 49 stateful · 2026-08-24 13:54:21 UTC
Parallelism
66/100
Blocked
78%
Avg conflicts / tx
2.91
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,774,982 · 68 txs across 23 waves · depth 23
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
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w310w417w519w623w724w837w438w842w246w947w1050w757w1259w1465w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xef1453ca…0053
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0xd59f6ed1…03e6
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity