← previous blocknext block →recent activity
Analyzing
Block #109,142,714
21 transactions · 18 stateful · 2026-09-29 21:25:18 UTC
Parallelism
62/100
Blocked
61%
Avg conflicts / tx
1.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,142,714 · 21 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
1w02w13w24w38w49w510w616w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xd4fe0ff1…46b6
0xd32edf…ff58
13 touches
21 conflicts
0x500e6948…adc3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x411a01cc…e443
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
21 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity