← previous blocknext block →recent activity

Analyzing

Block #107,817,134

27 transactions · 22 stateful · 2026-09-25 06:06:27 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #107,817,134  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8041f328…97e7

0x34b655…2a6f

8 touches
6 conflicts

0x93e9d6dc…6aea

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x69ee34d1…30f8

0x34b655…2a6f

8 touches
6 conflicts

0x641aed07…bcb9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5cf4d55d…c588

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x8041f328a9…b697e7

← previous block·next block →recent activity