← previous blocknext block →recent activity

Analyzing

Block #106,408,349

18 transactions · 15 stateful · 2026-09-20 07:52:11 UTC

Parallelism

72/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,408,349  ·  18 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

0xd1ed6c82…869d

0x34b655…2a6f

8 touches
6 conflicts

0x310a7246…2dcb

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x8fd9063d…2f57

0x34b655…2a6f

4 touches
1 conflict

0xb40e601f…bf98

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 0xd1ed6c827e…c8869d

← previous block·next block →recent activity