← previous blocknext block →recent activity
Analyzing
Block #98,217,474
35 transactions · 33 stateful · 2026-08-22 14:33:09 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
2.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,217,474 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w27w38w09w210w411w512w620w125w734w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x06ca28c8…0aee
0xd32edf…ff58
13 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x14af78bb…aedd
0x1b6862…e19c
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity