← previous blocknext block →recent activity
Analyzing
Block #100,566,711
30 transactions · 28 stateful · 2026-08-30 20:36:13 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,566,711 · 30 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
1w02w13w24w36w09w110w211w312w414w315w417w018w220w427w529w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e49348b…9445
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x55010ec8…ea31
0x34b655…2a6f
8 touches
6 conflicts
0x44bc2c65…2652
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
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
10 conflicts on slot 0x3e49348b38…839445
Audit this contract →
← previous block·next block →recent activity