← previous blocknext block →recent activity
Analyzing
Block #98,067,156
36 transactions · 34 stateful · 2026-08-22 01:56:07 UTC
Parallelism
53/100
Blocked
71%
Avg conflicts / tx
3.36
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,067,156 · 36 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
1w02w13w06w27w08w19w210w311w012w116w318w220w422w424w625w727w931w1333w1535w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0x7aad02c6…b979
0x34b655…2a6f
14 touches
21 conflicts
0x5c1b956d…14d3
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity