← previous blocknext block →recent activity
Analyzing
Block #98,772,745
62 transactions · 51 stateful · 2026-08-24 13:43:06 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
3.15
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,772,745 · 62 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w010w111w212w313w414w515w617w718w819w920w1021w1122w1223w1337w238w342w443w551w452w553w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
8 touches
6 conflicts
0x0a809ce1…7894
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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: 0xbb3f3cb7…74e046
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity