← previous blocknext block →recent activity
Analyzing
Block #98,379,529
43 transactions · 36 stateful · 2026-08-23 04:08:27 UTC
Parallelism
72/100
Blocked
72%
Avg conflicts / tx
1.95
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,379,529 · 43 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w29w011w112w213w314w316w217w318w419w520w621w722w827w438w739w840w941w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd305993f…8ee1
0xd32edf…ff58
7 touches
6 conflicts
0xd53220ed…4736
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0xbb3f3cb7…74e046
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity