← previous blocknext block →recent activity

Analyzing

Block #100,151,100

27 transactions · 26 stateful · 2026-08-29 09:41:12 UTC

Parallelism

70/100

Blocked

46%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,151,100  ·  27 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

0x24bb46f7…3853

0x34b655…2a6f

16 touches
28 conflicts

0xd66696e0…0842

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x2d4cd1ab…19b0

0x34b655…2a6f

8 touches
6 conflicts

0x9b9e2a0b…0498

0x34b655…2a6f

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

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

28 conflicts on slot 0x24bb46f739…c13853

← previous block·next block →recent activity