← previous blocknext block →recent activity
Analyzing
Block #101,660,310
21 transactions · 20 stateful · 2026-09-03 16:18:43 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,660,310 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w08w09w110w211w314w217w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd791576…6717
0x34b655…2a6f
8 touches
6 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xb40e601f…bf98
0x34b655…2a6f
8 touches
6 conflicts
0xc52785b9…08f8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf36124ad…c08f
0x34b655…2a6f
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
6 conflicts on slot 0xfd7915766a…406717
Audit this contract →
← previous block·next block →recent activity