← previous blocknext block →recent activity

Analyzing

Block #106,235,588

19 transactions · 18 stateful · 2026-09-19 17:22:47 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,235,588  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1b25f260…c429

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x2d071de0…c86e

0x34b655…2a6f

6 touches
3 conflicts

0x524f0872…0d12

0x34b655…2a6f

6 touches
3 conflicts

0x08545126…db41

0x34b655…2a6f

6 touches
3 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

4 touches
1 conflict

0xbd590df7…9891

0x34b655…2a6f

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

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

3 conflicts on slot 0x1b25f26097…52c429

← previous block·next block →recent activity