← previous blocknext block →recent activity

Analyzing

Block #105,576,135

20 transactions · 20 stateful · 2026-09-17 10:01:12 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,576,135  ·  20 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

0x02373c43…3cb3

0x34b655…2a6f

6 touches
3 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

6 touches
3 conflicts

0x7f7bf262…3534

0x34b655…2a6f

6 touches
3 conflicts

0xc4d98fb1…c354

0x40c49f…2af0

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xba1edffb…323e

0x34b655…2a6f

4 touches
1 conflict

0xc5847c4d…a65c

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 0x02373c432b…ff3cb3

← previous block·next block →recent activity