← previous blocknext block →recent activity
Analyzing
Block #98,013,752
77 transactions · 63 stateful · 2026-08-21 21:27:15 UTC
Parallelism
74/100
Blocked
68%
Avg conflicts / tx
3.21
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,013,752 · 77 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
1w02w03w04w18w29w310w411w513w614w715w827w132w433w535w656w576w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
34 touches
136 conflicts
0x17606ba6…1b6e
0x754704…b603
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x62c3bcda…93a5
0x754704…b603
14 touches
21 conflicts
0x56a919c4…ab49
0xee8c0e…1242
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
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
136 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity