← previous blocknext block →recent activity
Analyzing
Block #105,642,845
36 transactions · 34 stateful · 2026-09-17 15:37:01 UTC
Parallelism
64/100
Blocked
74%
Avg conflicts / tx
2.44
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,642,845 · 36 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w114w516w617w722w624w328w230w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xade0fbee…9ef5
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf2e7bb96…1a56
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 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity