← previous blocknext block →recent activity
Analyzing
Block #98,386,883
128 transactions · 73 stateful · 2026-08-23 04:45:26 UTC
Parallelism
81/100
Blocked
79%
Avg conflicts / tx
2.74
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #98,386,883 · 128 txs across 24 waves · depth 24
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
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w212w313w414w516w617w718w819w987w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0x737acb78…fce8
0x34b655…2a6f
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0xa6afd3…d132
22 touches
55 conflicts
0x17606ba6…1b6e
0x754704…b603
20 touches
45 conflicts
0xdb067026…9eb8
0x2b46c0…1669
16 touches
28 conflicts
0xf8f1e808…a4fd
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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity