← previous blocknext block →recent activity
Analyzing
Block #105,672,379
23 transactions · 22 stateful · 2026-09-17 18:05:42 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,672,379 · 23 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
1w02w13w24w35w47w215w316w417w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x37699b20…1073
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
28 conflicts on slot 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity