← previous blocknext block →recent activity
Analyzing
Block #98,729,226
70 transactions · 50 stateful · 2026-08-24 10:04:02 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
3.14
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,729,226 · 70 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
1w02w13w24w35w46w57w68w79w810w238w939w1046w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xe9564990…f541
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0029
0x1b6862…e19c
16 touches
28 conflicts
0x3a3097d7…2ab3
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 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