← previous blocknext block →recent activity
Analyzing
Block #106,566,094
28 transactions · 27 stateful · 2026-09-20 21:06:08 UTC
Parallelism
61/100
Blocked
63%
Avg conflicts / tx
2.07
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,566,094 · 28 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
1w02w13w24w35w46w59w012w013w115w616w317w418w520w721w823w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
14 touches
21 conflicts
0x663784e7…acb8
0x34b655…2a6f
12 touches
15 conflicts
0x87deba8b…bdc5
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf2e7bb96…1a59
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity