← previous blocknext block →recent activity

Analyzing

Block #106,458,251

21 transactions · 20 stateful · 2026-09-20 12:03:24 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.86

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,458,251  ·  21 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

0xc86aea27…5791

0x34b655…2a6f

18 touches
36 conflicts

0x0262e1c6…52e1

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x310a7246…2dcb

0x34b655…2a6f

8 touches
6 conflicts

0x172b0de5…980b

0x34b655…2a6f

8 touches
6 conflicts

0x159cff26…7665

0x34b655…2a6f

8 touches
6 conflicts

0xa3ed5a09…c6d3

0x34b655…2a6f

6 touches
3 conflicts

0xd706972e…9d0e

0x065c9d…c394

5 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

36 conflicts on slot 0xc86aea27c9…775791

← previous block·next block →recent activity