← previous blocknext block →recent activity
Analyzing
Block #105,608,580
35 transactions · 33 stateful · 2026-09-17 12:44:31 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,608,580 · 35 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
1w02w13w24w35w46w57w08w19w210w311w412w526w127w529w630w233w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69011797…547a
0x34b655…2a6f
16 touches
28 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x4979282b…2934
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0x69011797eb…7d547a
Audit this contract →
← previous block·next block →recent activity