← previous blocknext block →recent activity

Analyzing

Block #107,814,381

17 transactions · 17 stateful · 2026-09-25 05:52:36 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.47

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #107,814,381  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xcc844ab5…4c6d

0x34b655…2a6f

12 touches
15 conflicts

0xf369641d…cd00

0x34b655…2a6f

12 touches
15 conflicts

0xba522812…1f1f

0x34b655…2a6f

12 touches
15 conflicts

0xba5743c7…21c6

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x6c3c5312…d25d

0xd32edf…ff58

9 touches
10 conflicts

0x2130a548…c1de

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0xcc844ab542…814c6d

← previous block·next block →recent activity