← previous blocknext block →recent activity
Analyzing
Block #98,673,583
65 transactions · 54 stateful · 2026-08-24 05:19:56 UTC
Parallelism
71/100
Blocked
83%
Avg conflicts / tx
3.58
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,673,583 · 65 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w429w130w232w334w535w638w442w546w752w654w855w956w1059w1361w1562w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…0002
0xbb3f3c…e046
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
12 touches
15 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity