← previous blocknext block →recent activity
Analyzing
Block #106,185,978
113 transactions · 60 stateful · 2026-09-19 13:13:01 UTC
Parallelism
81/100
Blocked
75%
Avg conflicts / tx
3.26
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #106,185,978 · 113 txs across 22 waves · depth 22
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w27w39w450w573w774w875w978w1280w1381w1482w1583w1684w1786w18108w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
38 touches
171 conflicts
0xaf31f8bf…bf23
0xd32edf…ff58
25 touches
78 conflicts
0x708d7a74…09e3
0x34b655…2a6f
24 touches
66 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
22 touches
55 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…001e
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
22 touches
55 conflicts
0x65903ef9…2567
0x34b655…2a6f
18 touches
36 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
171 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity