← previous blocknext block →recent activity

Analyzing

Block #106,275,185

25 transactions · 23 stateful · 2026-09-19 20:42:03 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,275,185  ·  25 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

0xebc0acf9…26cb

0x34b655…2a6f

16 touches
28 conflicts

0xfb2b82e5…8fe6

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

8 touches
6 conflicts

0x5e2ea201…12de

0x34b655…2a6f

8 touches
6 conflicts

0x6b267bdf…b173

0x34b655…2a6f

8 touches
6 conflicts

0xac0b4a08…faae

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0xebc0acf9b3…c026cb

← previous block·next block →recent activity