← previous blocknext block →recent activity
Analyzing
Block #101,935,520
19 transactions · 18 stateful · 2026-09-04 15:24:53 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,935,520 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w17w08w29w010w011w112w013w114w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc921ce…dc0d
0x34b655…2a6f
6 touches
3 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
6 touches
3 conflicts
0xb58ed141…c32e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc853be2d…b18f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
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 0xffc921ce0e…2adc0d
Audit this contract →
← previous block·next block →recent activity