← previous blocknext block →recent activity
Analyzing
Block #102,252,471
24 transactions · 23 stateful · 2026-09-05 18:11:31 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,252,471 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w19w111w012w113w215w216w318w419w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0x6a4075a3…3d4f
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0xa256e538…fb75
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity