← previous blocknext block →recent activity
Analyzing
Block #99,038,373
87 transactions · 57 stateful · 2026-08-25 12:02:47 UTC
Parallelism
80/100
Blocked
70%
Avg conflicts / tx
2.14
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #99,038,373 · 87 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
1w03w05w06w19w014w116w017w118w219w021w123w126w228w329w432w533w635w738w354w158w865w9
- 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
16 touches
28 conflicts
0x9d929e0c…9421
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xb55f6c75…c2d2
0xa6afd3…d132
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x9a9383a9…6bc7
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: Perpl
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity