← previous blocknext block →recent activity
Analyzing
Block #98,079,909
50 transactions · 41 stateful · 2026-08-22 03:00:18 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.54
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,079,909 · 50 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
1w03w05w06w17w08w19w010w111w212w013w119w023w124w225w326w427w528w131w232w133w238w441w643w844w947w1249w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x62910921…3016
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xa56ae218…1fc5
0x34b655…2a6f
8 touches
6 conflicts
0x4635fb46…4cfd
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity