← previous blocknext block →recent activity

Analyzing

Block #106,956,052

20 transactions · 20 stateful · 2026-09-22 05:49:52 UTC

Parallelism

40/100

Blocked

75%

Avg conflicts / tx

3.45

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #106,956,052  ·  20 txs across 12 waves  ·  depth 12
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

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

0xfcd5e68f…2a12

0x34b655…2a6f

22 touches
55 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

20 touches
45 conflicts

0xce307d4a…b8d8

0x34b655…2a6f

18 touches
36 conflicts

0x4f089e20…f71a

0x34b655…2a6f

18 touches
36 conflicts

0xca841faa…486a

0x34b655…2a6f

18 touches
36 conflicts

0xa7d3cb90…e1d9

0x34b655…2a6f

16 touches
28 conflicts

0xabfdfd0e…20bf

0x34b655…2a6f

16 touches
28 conflicts

0xc11f059c…1eb9

0x34b655…2a6f

16 touches
28 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

55 conflicts on slot 0xfcd5e68f28…382a12

← previous block·next block →recent activity