← previous blocknext block →recent activity

Analyzing

Block #106,932,418

23 transactions · 20 stateful · 2026-09-22 03:50:54 UTC

Parallelism

52/100

Blocked

60%

Avg conflicts / tx

1.61

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,932,418  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xdde1e193…3893

0x34b655…2a6f

16 touches
28 conflicts

0x858e40c0…7e30

0x34b655…2a6f

14 touches
21 conflicts

0x4786839b…c29a

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0xc35d158c…6271

0x34b655…2a6f

8 touches
6 conflicts

0xea79e6d3…68ad

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

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 0xdde1e1937b…d03893

← previous block·next block →recent activity