← previous blocknext block →recent activity
Analyzing
Block #98,063,037
41 transactions · 33 stateful · 2026-08-22 01:35:24 UTC
Parallelism
66/100
Blocked
58%
Avg conflicts / tx
1.56
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,063,037 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w09w110w212w113w214w015w321w022w423w527w228w631w632w736w1038w1239w1340w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x3fb61494…573a
0x34b655…2a6f
8 touches
6 conflicts
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0x4e5996a0…68fd
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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