← previous blocknext block →recent activity
Analyzing
Block #105,576,521
50 transactions · 40 stateful · 2026-09-17 10:03:08 UTC
Parallelism
78/100
Blocked
63%
Avg conflicts / tx
1.34
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,576,521 · 50 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w08w110w011w112w013w014w115w216w017w018w119w020w022w124w226w027w128w230w131w233w334w235w136w137w241w243w449w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb0f5bc30…5d12
0x34b655…2a6f
6 touches
3 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity