← previous blocknext block →recent activity
Analyzing
Block #100,729,267
25 transactions · 24 stateful · 2026-08-31 10:13:57 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,729,267 · 25 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
1w04w05w06w17w28w311w412w015w518w619w721w122w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe570ac03…c100
0x34b655…2a6f
8 touches
6 conflicts
0x68531239…e9a3
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc5f336ca…912e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x54c6fb44…369a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
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
6 conflicts on slot 0xe570ac037a…8cc100
Audit this contract →
← previous block·next block →recent activity