← previous blocknext block →recent activity
Analyzing
Block #98,427,347
112 transactions · 103 stateful · 2026-08-23 08:09:02 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
1.68
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,427,347 · 112 txs across 23 waves · depth 23
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
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w117w221w322w423w532w288w889w391w498w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
14 touches
21 conflicts
0xd53220ed…4737
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity