← previous blocknext block →recent activity

Analyzing

Block #106,952,611

27 transactions · 27 stateful · 2026-09-22 05:32:33 UTC

Parallelism

67/100

Blocked

59%

Avg conflicts / tx

1.63

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,952,611  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x148c2efc…4410

0x34b655…2a6f

14 touches
21 conflicts

0x60b6cf89…9374

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x874c850e…c940

0x34b655…2a6f

6 touches
3 conflicts

0xfc0dbd5b…e713

0x34b655…2a6f

6 touches
3 conflicts

0x22cf0755…997d

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 0x148c2efc85…b34410

← previous block·next block →recent activity