← previous blocknext block →recent activity

Analyzing

Block #105,853,419

21 transactions · 19 stateful · 2026-09-18 09:18:16 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,853,419  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6caf33e2…c261

0x34b655…2a6f

10 touches
10 conflicts

0x6a4b9787…57b8

0x34b655…2a6f

8 touches
6 conflicts

0xab981df1…2941

0x34b655…2a6f

6 touches
3 conflicts

0x80398c66…f3cc

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xbb7c4b5c…6304

0x34b655…2a6f

4 touches
1 conflict

0x3018a378…d7bb

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