← previous blocknext block →recent activity
Analyzing
Block #98,536,395
41 transactions · 38 stateful · 2026-08-23 17:24:59 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
2.46
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,536,395 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w18w29w311w415w219w120w321w422w524w625w726w827w928w1029w1133w1236w537w638w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xfb0a4eb5…8be3
0x34b655…2a6f
12 touches
15 conflicts
0x0f44b5ba…e7bf
0x34b655…2a6f
12 touches
15 conflicts
0x52cf5603…ca01
0x34b655…2a6f
12 touches
15 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0x793aa64d…b09c
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity