← previous blocknext block →recent activity
Analyzing
Block #105,582,753
19 transactions · 16 stateful · 2026-09-17 10:34:30 UTC
Parallelism
58/100
Blocked
63%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,582,753 · 19 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
1w02w13w24w35w06w17w08w313w414w516w217w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f5707c2…cda2
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x03f64644…4068
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2f5707c2b3…3ccda2
Audit this contract →
← previous block·next block →recent activity