← previous blocknext block →recent activity
Analyzing
Block #102,217,635
24 transactions · 23 stateful · 2026-09-05 15:15:01 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,217,635 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w210w111w212w317w018w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xced4ddba…d164
0x34b655…2a6f
4 touches
1 conflict
0xf4077a52…07e1
0x34b655…2a6f
4 touches
1 conflict
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0x12a9b76e…cb76
0x3bd359…433a
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity