← previous blocknext block →recent activity
Analyzing
Block #100,441,112
21 transactions · 20 stateful · 2026-08-30 10:04:18 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,441,112 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w410w012w113w214w315w416w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef2d623…d293
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03e7
0x1b6862…e19c
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
10 conflicts on slot 0xcef2d6238e…78d293
Audit this contract →
← previous block·next block →recent activity