← previous blocknext block →recent activity
Analyzing
Block #105,626,259
43 transactions · 36 stateful · 2026-09-17 14:13:32 UTC
Parallelism
86/100
Blocked
58%
Avg conflicts / tx
1.02
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,626,259 · 43 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w318w228w329w336w237w438w439w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12e7c471…901c
0x34b655…2a6f
12 touches
15 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x45b67460…28a8
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 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 0x12e7c471ad…22901c
Audit this contract →
← previous block·next block →recent activity