← previous blocknext block →recent activity

Analyzing

Block #100,976,826

22 transactions · 21 stateful · 2026-09-01 06:59:38 UTC

Parallelism

55/100

Blocked

48%

Avg conflicts / tx

1.45

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #100,976,826  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xe1c4e5ce…0dec

0x34b655…2a6f

16 touches
28 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xbd590df7…9891

0x34b655…2a6f

14 touches
21 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

12 touches
15 conflicts

0x083a8763…5a7e

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1d1eb3d2…d573

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

28 conflicts on slot 0xe1c4e5ce15…770dec

← previous block·next block →recent activity