← previous blocknext block →recent activity

Analyzing

Block #100,920,099

25 transactions · 15 stateful · 2026-09-01 02:14:17 UTC

Parallelism

88/100

Blocked

47%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,920,099  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

6 touches
3 conflicts

0xd227a831…5862

0x065c9d…c394

5 touches
3 conflicts

0x6a5a8729…2be9

0xd32edf…ff58

5 touches
3 conflicts

0xc10b903d…2f54

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb419942f…703d

0x34b655…2a6f

4 touches
1 conflict

0x2827ae77…4368

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity