← previous blocknext block →recent activity
Analyzing
Block #98,082,136
33 transactions · 30 stateful · 2026-08-22 03:11:31 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.94
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,082,136 · 33 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
1w03w04w06w07w110w011w112w213w315w117w120w425w627w828w929w1030w1131w1232w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x21e8ab54…3b4b
0x34b655…2a6f
8 touches
6 conflicts
0xd3c05624…3417
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity