← previous blocknext block →recent activity
Analyzing
Block #102,649,948
18 transactions · 17 stateful · 2026-09-07 03:45:00 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,649,948 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w010w111w212w314w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaafbb394…5fb7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x1aefc3d2…66f5
0x34b655…2a6f
4 touches
1 conflict
0x247cfb80…cca8
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
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
6 conflicts on slot 0xaafbb39429…b55fb7
Audit this contract →
← previous block·next block →recent activity