← previous blocknext block →recent activity

Analyzing

Block #100,728,228

29 transactions · 26 stateful · 2026-08-31 10:08:43 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,728,228  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x5a95f394…be66

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xfdb6a6c8…31c4

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x26253352…1a75

0x34b655…2a6f

4 touches
1 conflict

0x53eac009…b61b

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity