← previous blocknext block →recent activity

Analyzing

Block #105,627,139

39 transactions · 34 stateful · 2026-09-17 14:17:58 UTC

Parallelism

82/100

Blocked

53%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,627,139  ·  39 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

0x7151b1ad…4520

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x1ef22441…7de3

0x34b655…2a6f

8 touches
6 conflicts

0x5ab4d7c5…c0f5

0x34b655…2a6f

8 touches
6 conflicts

0xba1edffb…323e

0x34b655…2a6f

8 touches
6 conflicts

0xd6980aa4…a052

0x34b655…2a6f

6 touches
3 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

21 conflicts on slot 0x7151b1adae…de4520

← previous block·next block →recent activity