← previous blocknext block →recent activity
Analyzing
Block #102,872,159
17 transactions · 14 stateful · 2026-09-07 22:26:13 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,872,159 · 17 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
1w08w09w110w111w212w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb2d8af24…4750
0x34b655…2a6f
6 touches
3 conflicts
0x910aab66…f893
0x34b655…2a6f
6 touches
3 conflicts
0x42c0a5d3…a476
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x77710b33…1c7b
0x34b655…2a6f
4 touches
1 conflict
0x93f1d5e2…928f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity