← previous blocknext block →recent activity
Analyzing
Block #105,643,504
38 transactions · 36 stateful · 2026-09-17 15:40:20 UTC
Parallelism
74/100
Blocked
72%
Avg conflicts / tx
2.55
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,643,504 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w811w322w436w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeddebb1d…4dd4
0x34b655…2a6f
18 touches
36 conflicts
0x3dc2c39f…c182
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
16 touches
28 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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
36 conflicts on slot 0xeddebb1d0b…f54dd4
Audit this contract →
← previous block·next block →recent activity