← previous blocknext block →recent activity

Analyzing

Block #105,600,909

32 transactions · 30 stateful · 2026-09-17 12:05:53 UTC

Parallelism

84/100

Blocked

20%

Avg conflicts / tx

0.28

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,600,909  ·  32 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

0x90a021f0…f922

0x34b655…2a6f

6 touches
3 conflicts

0xebb3362b…41f4

0x34b655…2a6f

6 touches
3 conflicts

0x1f396cee…862f

0x34b655…2a6f

4 touches
1 conflict

0x27b6010e…e4aa

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x5ddc4a77…765e

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7d0eaae2…60b7

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

3 conflicts on slot 0x90a021f05c…17f922

← previous block·next block →recent activity