← previous blocknext block →recent activity
Analyzing
Block #106,458,255
21 transactions · 21 stateful · 2026-09-20 12:03:25 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,458,255 · 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
1w02w13w24w35w46w57w010w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc86aea27…5791
0x34b655…2a6f
16 touches
28 conflicts
0xe1e01c87…ed7e
0xd32edf…ff58
11 touches
15 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
10 touches
10 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xd59f6ed1…03e8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0xc86aea27c9…775791
Audit this contract →
← previous block·next block →recent activity