← previous blocknext block →recent activity

Analyzing

Block #105,642,579

26 transactions · 21 stateful · 2026-09-17 15:35:41 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

0.88

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #105,642,579  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xeb5b61a2…b2bc

0x34b655…2a6f

10 touches
10 conflicts

0x0efc210e…70ab

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd54fbaaf…cb37

0x34b655…2a6f

6 touches
3 conflicts

0x6d43ee99…bdd6

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity