← previous blocknext block →recent activity
Analyzing
Block #109,142,717
16 transactions · 16 stateful · 2026-09-29 21:25:19 UTC
Parallelism
31/100
Blocked
69%
Avg conflicts / tx
3.19
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #109,142,717 · 16 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w711w713w814w915w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
14 touches
21 conflicts
0x505ddd03…3f60
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0019
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0029
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0052
0x1b6862…e19c
12 touches
15 conflicts
0x5e86ca39…99d6
0x1b6862…e19c
12 touches
15 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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity