← previous blocknext block →recent activity
Analyzing
Block #98,563,346
126 transactions · 90 stateful · 2026-08-23 19:45:39 UTC
Parallelism
82/100
Blocked
86%
Avg conflicts / tx
3.68
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,563,346 · 126 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w614w154w464w769w280w1083w1298w13112w1113w9114w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
38 touches
171 conflicts
0x261cbea7…e35d
0x34b655…2a6f
24 touches
66 conflicts
0x14c19746…a67e
0xd32edf…ff58
21 touches
55 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x523de645…4f58
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x7de57974…f5ba
0x34b655…2a6f
12 touches
15 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
171 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity