← previous blocknext block →recent activity

Analyzing

Block #105,634,255

18 transactions · 18 stateful · 2026-09-17 14:53:47 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,634,255  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x86d39701…e8ea

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf72228f6…970c

0x34b655…2a6f

6 touches
3 conflicts

0xa35509fa…5cb3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c2

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x22e0cc1d…ad0d

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

6 conflicts on slot 0x86d3970136…a1e8ea

← previous block·next block →recent activity