← previous blocknext block →recent activity

Analyzing

Block #107,841,651

31 transactions · 25 stateful · 2026-09-25 08:09:51 UTC

Parallelism

84/100

Blocked

28%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,841,651  ·  31 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

0x508174fb…94d2

0x34b655…2a6f

10 touches
10 conflicts

0xc1da8f73…484c

0x34b655…2a6f

8 touches
6 conflicts

0xf51ec09c…b4a9

0x34b655…2a6f

8 touches
6 conflicts

0x4a013ed4…bfa8

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x1d219442…2d8e

0x34b655…2a6f

6 touches
3 conflicts

0x6e0f1dd3…db06

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

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

10 conflicts on slot 0x508174fbc3…8094d2

← previous block·next block →recent activity