← previous blocknext block →recent activity
Analyzing
Block #105,542,967
34 transactions · 32 stateful · 2026-09-17 07:14:15 UTC
Parallelism
71/100
Blocked
66%
Avg conflicts / tx
1.82
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,542,967 · 34 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
1w02w13w24w35w46w57w08w19w511w214w315w423w524w626w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08687f0e…7a27
0x34b655…2a6f
12 touches
15 conflicts
0x29633b82…ba2a
0xd32edf…ff58
11 touches
15 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
10 touches
10 conflicts
0xbbe2df09…d681
0x34b655…2a6f
10 touches
10 conflicts
0xfa324e43…8895
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x4118bd12…924a
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 0x08687f0e65…107a27
Audit this contract →
← previous block·next block →recent activity