← previous blocknext block →recent activity
Analyzing
Block #100,793,706
24 transactions · 23 stateful · 2026-08-31 15:38:17 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
1.08
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,793,706 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w29w011w112w013w214w315w216w119w020w121w322w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x485d2778…aa5c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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: 0x851145ea…9f3f07
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity