← previous blocknext block →recent activity

Analyzing

Block #106,932,512

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

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,932,512  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfcef6587…476d

0x34b655…2a6f

12 touches
15 conflicts

0x858e40c0…7e30

0x34b655…2a6f

10 touches
10 conflicts

0x85bfd0af…ce96

0x34b655…2a6f

8 touches
6 conflicts

0x574628e9…dcc3

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x76cc3e39…f638

0x34b655…2a6f

6 touches
3 conflicts

0xba1edffb…323e

0x34b655…2a6f

6 touches
3 conflicts

0xd4230a60…bd13

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

15 conflicts on slot 0xfcef65879d…72476d

← previous block·next block →recent activity