← previous blocknext block →recent activity

Analyzing

Block #100,159,173

24 transactions · 20 stateful · 2026-08-29 10:21:51 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,159,173  ·  24 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

0x030939d3…a0eb

0x34b655…2a6f

6 touches
3 conflicts

0x07bb3f5a…617e

0x34b655…2a6f

6 touches
3 conflicts

0x0bf8c19b…42f3

0x34b655…2a6f

4 touches
1 conflict

0x0e3b59e9…d9d0

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x56a284d9…32e4

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 0x030939d3cd…65a0eb

← previous block·next block →recent activity