← previous blocknext block →recent activity

Analyzing

Block #100,455,371

22 transactions · 21 stateful · 2026-08-30 11:16:07 UTC

Parallelism

64/100

Blocked

62%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,455,371  ·  22 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

0x6a9f62ce…fa8c

0x34b655…2a6f

10 touches
10 conflicts

0x3e6302c8…64f5

0x34b655…2a6f

8 touches
6 conflicts

0xcd30dd02…d0e8

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xcf61f287…3f4e

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

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 0x6a9f62ce28…9cfa8c

← previous block·next block →recent activity