← previous blocknext block →recent activity
Analyzing
Block #99,114,919
29 transactions · 28 stateful · 2026-08-25 18:31:26 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,114,919 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w29w010w115w216w317w418w523w224w325w426w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0xa01f6d1b…4adf
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity