← previous blocknext block →recent activity
Analyzing
Block #98,527,062
53 transactions · 47 stateful · 2026-08-23 16:36:27 UTC
Parallelism
51/100
Blocked
77%
Avg conflicts / tx
4.62
Longest chain
26 deep
Execution timeline
did this block parallelize well?
view
block #98,527,062 · 53 txs across 26 waves · depth 26
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
wave w23
wave w24
wave w25
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w317w418w219w520w621w725w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
36 touches
153 conflicts
0x383782ee…41f7
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002d
0x1b6862…e19c
14 touches
21 conflicts
0xd25997d0…a688
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
153 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity