← previous blocknext block →recent activity
Analyzing
Block #102,050,157
20 transactions · 20 stateful · 2026-09-05 01:05:59 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,050,157 · 20 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
1w02w13w24w05w37w08w19w212w313w414w515w617w718w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0xe21a94dd…4838
0x34b655…2a6f
8 touches
6 conflicts
0xcc8b6d32…6601
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity