← previous blocknext block →recent activity

Analyzing

Block #100,082,192

23 transactions · 21 stateful · 2026-08-29 03:54:08 UTC

Parallelism

57/100

Blocked

57%

Avg conflicts / tx

2.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #100,082,192  ·  23 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

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0x627738d1…db02

0x34b655…2a6f

10 touches
10 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x8aa54923…53d6

0x34b655…2a6f

8 touches
6 conflicts

0xfaf89f45…ced6

0x34b655…2a6f

8 touches
6 conflicts

0x0ed7cc0b…ee52

0x34b655…2a6f

6 touches
3 conflicts

0xc20bb30f…7331

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity