← previous blocknext block →recent activity
Analyzing
Block #102,015,609
20 transactions · 20 stateful · 2026-09-04 22:11:04 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,015,609 · 20 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
1w02w13w25w16w27w38w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xc9ca92b3…ac3f
0x34b655…2a6f
10 touches
10 conflicts
0x5f749304…d1c1
0x34b655…2a6f
10 touches
10 conflicts
0x9c088939…ddd7
0x34b655…2a6f
8 touches
6 conflicts
0x9bff3222…a246
0x34b655…2a6f
8 touches
6 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
8 touches
6 conflicts
0x67043b0b…97d7
0x34b655…2a6f
8 touches
6 conflicts
0x02372d42…1871
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
10 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity