← previous blocknext block →recent activity

Analyzing

Block #100,084,382

21 transactions · 20 stateful · 2026-08-29 04:05:09 UTC

Parallelism

48/100

Blocked

55%

Avg conflicts / tx

2.24

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #100,084,382  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x44696fac…44d6

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0xaba6578d…bd48

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity