← previous blocknext block →recent activity

Analyzing

Block #100,454,900

17 transactions · 14 stateful · 2026-08-30 11:13:45 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,454,900  ·  17 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

0xcc282b3d…e139

0x34b655…2a6f

4 touches
1 conflict

0xcd30dd02…d0e8

0x34b655…2a6f

4 touches
1 conflict

0xf8e6479f…f193

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x29e8d1e2…e396

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x54f7f60f…43cc

0x34b655…2a6f

4 touches
1 conflict

0x699ee60f…de01

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

1 conflict on slot 0xcc282b3d26…31e139

← previous block·next block →recent activity