← previous blocknext block →recent activity
Analyzing
Block #98,645,535
21 transactions · 21 stateful · 2026-08-24 02:53:38 UTC
Parallelism
62/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,645,535 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w07w08w110w111w113w115w216w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
11 touches
15 conflicts
0xf98db8ee…a56d
0x34b655…2a6f
10 touches
10 conflicts
0x1c645adf…cd53
0x34b655…2a6f
9 touches
10 conflicts
0xaa179075…fdee
0x34b655…2a6f
5 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity