← previous blocknext block →recent activity
Analyzing
Block #98,645,602
18 transactions · 16 stateful · 2026-08-24 02:54:00 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,645,602 · 18 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
1w02w03w15w18w010w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x886db264…846e
0x34b655…2a6f
11 touches
15 conflicts
0xf98db8ee…a56d
0x34b655…2a6f
10 touches
10 conflicts
0x2b5cb9f0…1d10
0x34b655…2a6f
8 touches
6 conflicts
0x1c645adf…cd53
0x34b655…2a6f
7 touches
6 conflicts
0xa18a0b99…9d4d
0x34b655…2a6f
5 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity