← previous blocknext block →recent activity

Analyzing

Block #106,381,853

41 transactions · 35 stateful · 2026-09-20 05:38:51 UTC

Parallelism

68/100

Blocked

54%

Avg conflicts / tx

1.63

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #106,381,853  ·  41 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xba33378a…f1df

0x34b655…2a6f

18 touches
36 conflicts

0x3934e758…1dea

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0dd3d3cd…7281

0x34b655…2a6f

8 touches
6 conflicts

0x2c2761c0…476e

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0xe283e878…7262

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

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

36 conflicts on slot 0xba33378abc…73f1df

← previous block·next block →recent activity