← previous blocknext block →recent activity
Analyzing
Block #109,004,204
26 transactions · 23 stateful · 2026-09-29 09:46:41 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,004,204 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w516w517w018w119w220w321w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5b08e9b…22f7
0x34b655…2a6f
12 touches
15 conflicts
0xdba70be9…8b6b
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x063eca74…c2e2
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
15 conflicts on slot 0xa5b08e9b90…8322f7
Audit this contract →
← previous block·next block →recent activity