← previous blocknext block →recent activity
Analyzing
Block #100,589,713
50 transactions · 39 stateful · 2026-08-30 22:31:56 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
1.62
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,589,713 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w19w010w011w112w213w314w415w517w618w721w822w925w126w127w228w330w132w437w544w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
20 touches
45 conflicts
0x76622fb2…4f08
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1d9154e7…8821
0x34b655…2a6f
6 touches
3 conflicts
0x39f96589…5188
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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: 0xf5b5f7f8…a36d70
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity