← previous blocknext block →recent activity
Analyzing
Block #98,380,245
66 transactions · 58 stateful · 2026-08-23 04:12:03 UTC
Parallelism
70/100
Blocked
76%
Avg conflicts / tx
3.35
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,380,245 · 66 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
1w02w13w24w35w46w526w427w128w639w440w552w755w956w1059w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x00000000…0002
0xbb3f3c…e046
20 touches
45 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
12 touches
15 conflicts
0xb2acd93a…7996
0xd32edf…ff58
11 touches
15 conflicts
0x69017fce…85bd
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity