← previous blocknext block →recent activity

Analyzing

Block #107,849,568

33 transactions · 30 stateful · 2026-09-25 08:49:42 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,849,568  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x981254c6…2e26

0x34b655…2a6f

8 touches
6 conflicts

0xba522812…1f1f

0x34b655…2a6f

8 touches
6 conflicts

0x2b76a1fb…fdfc

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x88188d2d…2a76

0x34b655…2a6f

8 touches
6 conflicts

0xab41643c…f9bf

0x34b655…2a6f

6 touches
3 conflicts

0xcb21158b…f18d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

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

6 conflicts on slot 0x981254c6a9…732e26

← previous block·next block →recent activity