← previous blocknext block →recent activity

Analyzing

Block #106,535,084

27 transactions · 26 stateful · 2026-09-20 18:30:05 UTC

Parallelism

74/100

Blocked

46%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,535,084  ·  27 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

0x0fc536fb…1aa1

0x34b655…2a6f

14 touches
21 conflicts

0xa38ecced…a3be

0x34b655…2a6f

12 touches
15 conflicts

0xa705f083…67b4

0x34b655…2a6f

8 touches
6 conflicts

0xb2560305…f27d

0x34b655…2a6f

8 touches
6 conflicts

0xbaf6ed88…c179

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x028892a4…90ac

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 0x0fc536fb1f…c81aa1

← previous block·next block →recent activity