← previous blocknext block →recent activity
Analyzing
Block #102,189,149
21 transactions · 21 stateful · 2026-09-05 12:50:43 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,189,149 · 21 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
1w02w13w27w08w09w111w112w213w314w417w519w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b153079…4318
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
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 0x9b15307984…dd4318
Audit this contract →
← previous block·next block →recent activity