← previous blocknext block →recent activity
Analyzing
Block #98,673,535
51 transactions · 49 stateful · 2026-08-24 05:19:41 UTC
Parallelism
61/100
Blocked
49%
Avg conflicts / tx
2.35
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,673,535 · 51 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w010w011w112w113w214w316w217w018w420w524w625w735w841w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xbd590df7…9891
0x34b655…2a6f
18 touches
36 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
18 touches
36 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
18 touches
36 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity