← previous blocknext block →recent activity
Analyzing
Block #101,150,416
21 transactions · 19 stateful · 2026-09-01 21:33:19 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,150,416 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w08w19w011w114w217w018w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x869e74e8…d5d9
0xa6afd3…d132
6 touches
3 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
6 touches
3 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe06deacd…bab9
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity