← previous blocknext block →recent activity

Analyzing

Block #100,141,568

18 transactions · 17 stateful · 2026-08-29 08:53:14 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,141,568  ·  18 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

0xb2f9b22c…28ca

0x34b655…2a6f

10 touches
10 conflicts

0x7401eb95…986b

0x34b655…2a6f

8 touches
6 conflicts

0x4e58deff…c5d0

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0x5ed1f9d0…fc7f

0x34b655…2a6f

6 touches
3 conflicts

0x6183ee9a…21b1

0x34b655…2a6f

6 touches
3 conflicts

0x676f9f01…a8ac

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

10 conflicts on slot 0xb2f9b22cac…5928ca

← previous block·next block →recent activity