← previous blocknext block →recent activity
Analyzing
Block #98,453,406
22 transactions · 20 stateful · 2026-08-23 10:20:08 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,453,406 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w28w311w412w514w015w616w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb5f5f775…010b
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x8fef34d2…35eb
0x34b655…2a6f
9 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xf3bc99c2…069f
0x34b655…2a6f
6 touches
3 conflicts
0x9c2fc330…0091
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity