← previous blocknext block →recent activity

Analyzing

Block #100,923,362

24 transactions · 21 stateful · 2026-09-01 02:30:42 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,923,362  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x261cbea7…e35e

0x34b655…2a6f

6 touches
3 conflicts

0xb5924647…4cf1

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35d

0x34b655…2a6f

6 touches
3 conflicts

0x3662991e…cacc

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4557124d…0715

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 0xc824469a90…af6425

← previous block·next block →recent activity