← previous blocknext block →recent activity
Analyzing
Block #98,752,349
45 transactions · 36 stateful · 2026-08-24 12:00:23 UTC
Parallelism
62/100
Blocked
67%
Avg conflicts / tx
2.31
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,752,349 · 45 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
1w02w18w09w111w012w115w216w317w318w422w523w636w837w938w1039w1142w1444w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x71139dc6…77c7
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x489d7033…e8e1
0x34b655…2a6f
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity