← previous blocknext block →recent activity
Analyzing
Block #100,789,186
35 transactions · 34 stateful · 2026-08-31 15:15:31 UTC
Parallelism
69/100
Blocked
71%
Avg conflicts / tx
3.23
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,789,186 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w410w519w420w521w622w723w825w928w629w730w831w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x703260e6…602f
0xd32edf…ff58
15 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
12 touches
15 conflicts
0xcad937e9…786e
0x1b6862…e19c
12 touches
15 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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity