← previous blocknext block →recent activity
Analyzing
Block #100,227,306
26 transactions · 23 stateful · 2026-08-29 16:04:49 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,227,306 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w07w18w09w111w017w219w120w221w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xc5f276dc…57fa
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x394c3833…b4ae
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity