← previous blocknext block →recent activity

Analyzing

Block #105,858,663

21 transactions · 20 stateful · 2026-09-18 09:44:40 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,858,663  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd6349eea…0f57

0x6f6493…b480

6 touches
3 conflicts

0xe0b7bb02…36b3

0x6f6493…b480

6 touches
3 conflicts

0x025e9401…5593

0x6f6493…b480

6 touches
3 conflicts

0x0aff941a…8903

0x6f6493…b480

6 touches
3 conflicts

0x18d40cc5…72e4

0x6f6493…b480

6 touches
3 conflicts

0x22b1a3c2…5545

0x6f6493…b480

6 touches
3 conflicts

0x316ca3b4…f8e6

0x6f6493…b480

6 touches
3 conflicts

0x3f6a2f6b…5a32

0x6f6493…b480

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: 0x6f6493e3…08b480

3 conflicts on slot 0xd6349eea8f…2a0f57

← previous block·next block →recent activity