← previous blocknext block →recent activity
Analyzing
Block #98,334,930
91 transactions · 73 stateful · 2026-08-23 00:24:05 UTC
Parallelism
74/100
Blocked
77%
Avg conflicts / tx
3.87
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #98,334,930 · 91 txs across 24 waves · depth 24
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w19w210w013w114w217w318w419w544w645w746w847w969w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
36 touches
153 conflicts
0x889d5e90…929a
0x2a68ba…90c5
28 touches
91 conflicts
0x00000000…003d
0xa6afd3…d132
26 touches
78 conflicts
0x5778d110…d2e6
0xc8689a…ee79
24 touches
66 conflicts
0x0161566e…abb2
0xa6afd3…d132
24 touches
66 conflicts
0x68106229…7057
0xa6afd3…d132
24 touches
66 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
22 touches
55 conflicts
0xdb067026…9eb8
0x2b46c0…1669
22 touches
55 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