← previous blocknext block →recent activity

Analyzing

Block #106,015,435

21 transactions · 21 stateful · 2026-09-18 22:54:45 UTC

Parallelism

38/100

Blocked

62%

Avg conflicts / tx

3.71

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #106,015,435  ·  21 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

0xe1c4e5ce…0dec

0x34b655…2a6f

24 touches
66 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

24 touches
66 conflicts

0xca841faa…486a

0x34b655…2a6f

22 touches
55 conflicts

0xcdcaadcf…1c9f

0x34b655…2a6f

22 touches
55 conflicts

0xe0e514b5…590b

0x34b655…2a6f

22 touches
55 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

20 touches
45 conflicts

0x69d2053b…935a

0x34b655…2a6f

20 touches
45 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

20 touches
45 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

66 conflicts on slot 0xe1c4e5ce15…770dec

← previous block·next block →recent activity