← previous blocknext block →recent activity
Analyzing
Block #106,931,050
28 transactions · 26 stateful · 2026-09-22 03:44:01 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,931,050 · 28 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
1w02w13w24w35w16w28w39w413w314w121w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3f3795a…7a6c
0x34b655…2a6f
14 touches
21 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x61da5094…a3c9
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x4979282b…2936
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
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 0xf3f3795af4…727a6c
Audit this contract →
← previous block·next block →recent activity