← previous blocknext block →recent activity
Analyzing
Block #106,917,892
27 transactions · 25 stateful · 2026-09-22 02:37:47 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,892 · 27 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
1w02w13w24w35w47w011w112w214w215w316w518w619w420w521w622w725w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06e2d929…1d3e
0x34b655…2a6f
16 touches
28 conflicts
0x518221db…65f7
0x34b655…2a6f
12 touches
15 conflicts
0x4786839b…c29a
0x34b655…2a6f
10 touches
10 conflicts
0xf97962f7…1d61
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
28 conflicts on slot 0x06e2d929ca…231d3e
Audit this contract →
← previous block·next block →recent activity