← previous blocknext block →recent activity
Analyzing
Block #102,252,765
17 transactions · 17 stateful · 2026-09-05 18:13:00 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,252,765 · 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
1w02w13w25w06w08w19w210w312w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x048bf5ac…2c07
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
6 touches
3 conflicts
0xf5d28bce…c32c
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
6 touches
3 conflicts
0x46c14e01…ff09
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity