← previous blocknext block →recent activity

Analyzing

Block #107,785,577

24 transactions · 22 stateful · 2026-09-25 03:27:30 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,785,577  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfd4e632c…e14c

0x34b655…2a6f

10 touches
10 conflicts

0xb8acd6db…8581

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xc1507bef…1e9f

0xd32edf…ff58

9 touches
10 conflicts

0x4a45b318…9716

0x34b655…2a6f

8 touches
6 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

8 touches
6 conflicts

0x85473e46…670e

0x34b655…2a6f

8 touches
6 conflicts

0xaa654491…2ca4

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

10 conflicts on slot 0xfd4e632c76…e1e14c

← previous block·next block →recent activity