← previous blocknext block →recent activity
Analyzing
Block #105,626,291
39 transactions · 35 stateful · 2026-09-17 14:13:41 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,626,291 · 39 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
1w02w13w24w35w46w57w68w09w114w322w425w728w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f5e33f…719c
0x34b655…2a6f
12 touches
15 conflicts
0x7ddb6262…ea31
0xd32edf…ff58
11 touches
15 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x93afca4c…b47b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
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 0xe8f5e33f0f…b6719c
Audit this contract →
← previous block·next block →recent activity