← previous blocknext block →recent activity

Analyzing

Block #105,855,269

21 transactions · 19 stateful · 2026-09-18 09:27:35 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

0.76

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,855,269  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd63857dd…6d47

0x34b655…2a6f

8 touches
6 conflicts

0xd911522b…e960

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7c51d9aa…af39

0x34b655…2a6f

6 touches
3 conflicts

0x0efc210e…70ab

0x34b655…2a6f

6 touches
3 conflicts

0x2827ae77…4368

0x34b655…2a6f

6 touches
3 conflicts

0xdb95e18e…c737

0x1b6862…e19c

4 touches
1 conflict

0x42522e76…2592

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

6 conflicts on slot 0xd63857dd2f…bc6d47

← previous block·next block →recent activity