← previous blocknext block →recent activity
Analyzing
Block #102,650,109
41 transactions · 34 stateful · 2026-09-07 03:45:48 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
2.05
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #102,650,109 · 41 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w09w112w213w315w216w317w418w421w325w526w628w730w132w234w339w1040w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb16deb8e…f7a5
0xd32edf…ff58
11 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xcb804507…d2d6
0x34b655…2a6f
10 touches
10 conflicts
0xd1203697…1ae0
0x40c49f…2af0
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity