← previous blocknext block →recent activity

Analyzing

Block #105,880,959

16 transactions · 15 stateful · 2026-09-18 11:36:52 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,880,959  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x011aaab0…c33c

0x6f6493…b480

10 touches
10 conflicts

0x08531a14…ed6e

0x6f6493…b480

10 touches
10 conflicts

0x0e3e4037…7a7a

0x6f6493…b480

10 touches
10 conflicts

0x17ceff23…d3dc

0x6f6493…b480

10 touches
10 conflicts

0x26e4ea9e…aa99

0x6f6493…b480

10 touches
10 conflicts

0x2af13d5c…9d70

0x6f6493…b480

10 touches
10 conflicts

0x32cbace5…f975

0x6f6493…b480

10 touches
10 conflicts

0x47ab30b7…65b6

0x6f6493…b480

10 touches
10 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

10 conflicts on slot 0x011aaab01c…90c33c

← previous block·next block →recent activity