← previous blocknext block →recent activity
Analyzing
Block #98,379,574
53 transactions · 44 stateful · 2026-08-23 04:08:40 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.28
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,379,574 · 53 txs across 19 waves · depth 19
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
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w18w09w110w411w512w613w114w228w429w631w434w145w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0xd541a808…4002
0x34b655…2a6f
10 touches
10 conflicts
0x262ccc22…818f
0xd32edf…ff58
9 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity