← previous blocknext block →recent activity
Analyzing
Block #105,849,547
68 transactions · 58 stateful · 2026-09-18 08:58:47 UTC
Parallelism
65/100
Blocked
76%
Avg conflicts / tx
4
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #105,849,547 · 68 txs across 24 waves · depth 24
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
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w940w1042w143w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x6f404efe…b0e3
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…001f
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002f
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0xf2e7bb96…1a5a
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
78 conflicts on slot 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity