← previous blocknext block →recent activity

Analyzing

Block #100,228,540

17 transactions · 17 stateful · 2026-08-29 16:11:02 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,228,540  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2c0c3e3f…5849

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0x4f3a6b4a…3819

0x34b655…2a6f

4 touches
1 conflict

0xb0f5d668…99ac

0x34b655…2a6f

4 touches
1 conflict

0xbceecf11…0120

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 0x2c0c3e3f10…6c5849

← previous block·next block →recent activity