← previous blocknext block →recent activity
Analyzing
Block #98,384,001
40 transactions · 36 stateful · 2026-08-23 04:30:57 UTC
Parallelism
57/100
Blocked
69%
Avg conflicts / tx
2.9
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,384,001 · 40 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w29w310w411w513w218w319w420w521w622w132w933w1037w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x8b41ec8f…c2d5
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x0299d0eb…ce68
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity