← previous blocknext block →recent activity
Analyzing
Block #98,913,545
38 transactions · 38 stateful · 2026-08-25 01:31:40 UTC
Parallelism
55/100
Blocked
66%
Avg conflicts / tx
2.76
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,913,545 · 38 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w210w011w112w215w216w317w418w525w227w628w729w830w932w1136w1537w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
8 touches
6 conflicts
0x801e9566…9d4c
0x34b655…2a6f
8 touches
6 conflicts
0xf6baac03…62ca
0x34b655…2a6f
7 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