← previous blocknext block →recent activity
Analyzing
Block #105,855,416
24 transactions · 24 stateful · 2026-09-18 09:28:19 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,855,416 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w111w212w314w515w616w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
12 touches
15 conflicts
0x884cfd8a…51c6
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x1f8a126c…9aa1
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
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
15 conflicts on slot 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity