← previous blocknext block →recent activity
Analyzing
Block #98,605,607
40 transactions · 35 stateful · 2026-08-23 23:26:00 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
2.15
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,605,607 · 40 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w49w011w012w114w215w317w019w120w421w522w423w526w627w728w331w634w936w1137w1238w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
8 touches
6 conflicts
0x0be16f1a…0dc7
0x34b655…2a6f
8 touches
6 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity