← previous blocknext block →recent activity
Analyzing
Block #99,473,340
48 transactions · 42 stateful · 2026-08-27 00:35:28 UTC
Parallelism
60/100
Blocked
71%
Avg conflicts / tx
2.65
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #99,473,340 · 48 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
1w02w13w24w35w17w28w310w411w513w316w432w437w841w1243w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
10 touches
10 conflicts
0x53e50026…6d8c
0x2b46c0…1669
10 touches
10 conflicts
0x6eff310a…c34c
0x2b46c0…1669
10 touches
10 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity