← previous blocknext block →recent activity
Analyzing
Block #101,315,227
23 transactions · 21 stateful · 2026-09-02 11:22:29 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,315,227 · 23 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
5w06w08w19w214w315w416w417w522w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8571fbdb…345a
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe166efa6…8d7b
0x34b655…2a6f
6 touches
3 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
6 touches
3 conflicts
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0xec1d6663…6042
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
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
10 conflicts on slot 0x8571fbdb53…aa345a
Audit this contract →
← previous block·next block →recent activity