← previous blocknext block →recent activity
Analyzing
Block #102,019,713
20 transactions · 18 stateful · 2026-09-04 22:31:49 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,019,713 · 20 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
1w02w13w24w36w07w116w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xaf199a64…16ed
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x3b25d07f…1dee
0x34b655…2a6f
6 touches
3 conflicts
0x55fc72dc…f3c5
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x7e273bc0…5dbc
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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity