← previous blocknext block →recent activity

Analyzing

Block #106,397,027

21 transactions · 20 stateful · 2026-09-20 06:55:13 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,397,027  ·  21 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

0xf61f6eb5…1413

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

6 touches
3 conflicts

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0x0463db49…5d05

0x34b655…2a6f

6 touches
3 conflicts

0x8379d944…cc17

0x34b655…2a6f

6 touches
3 conflicts

0xbaf6ed88…c179

0x34b655…2a6f

6 touches
3 conflicts

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

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

6 conflicts on slot 0xf61f6eb53f…251413

← previous block·next block →recent activity