← previous blocknext block →recent activity

Analyzing

Block #106,958,086

24 transactions · 22 stateful · 2026-09-22 06:00:06 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,958,086  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x77058d1a…4dd8

0x34b655…2a6f

16 touches
28 conflicts

0x01ad5dd0…11a1

0x34b655…2a6f

10 touches
10 conflicts

0x53ca1284…cb2c

0x34b655…2a6f

8 touches
6 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

8 touches
6 conflicts

0xc8c615d4…5da3

0x34b655…2a6f

8 touches
6 conflicts

0xd9a74048…63af

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

6 touches
3 conflicts

0x5fad6fee…7714

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

28 conflicts on slot 0x77058d1af4…9a4dd8

← previous block·next block →recent activity