← previous blocknext block →recent activity
Analyzing
Block #102,349,068
22 transactions · 21 stateful · 2026-09-06 02:21:00 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,349,068 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w27w110w111w212w315w416w517w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16d9a25c…635b
0x34b655…2a6f
12 touches
15 conflicts
0x53c41998…7d52
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xeb0b1d43…9559
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd6a0a7b8…fb34
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x718a859d…2d18
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
15 conflicts on slot 0x16d9a25c3b…91635b
Audit this contract →
← previous block·next block →recent activity