← previous blocknext block →recent activity

Analyzing

Block #105,931,903

22 transactions · 19 stateful · 2026-09-18 15:54:10 UTC

Parallelism

77/100

Blocked

37%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,931,903  ·  22 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

0xbc8fb280…76a3

0x34b655…2a6f

10 touches
10 conflicts

0x12e605da…9ca3

0x34b655…2a6f

8 touches
6 conflicts

0x12e77486…ec2b

0x34b655…2a6f

8 touches
6 conflicts

0x309f47c0…e1cf

0x34b655…2a6f

8 touches
6 conflicts

0x3b65c5ca…9f83

0x34b655…2a6f

8 touches
6 conflicts

0x3c9b10c1…d791

0x34b655…2a6f

8 touches
6 conflicts

0x55cde02d…89cb

0x34b655…2a6f

8 touches
6 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

8 touches
6 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: Perpl

10 conflicts on slot 0xbc8fb28081…2176a3

← previous block·next block →recent activity