← previous blocknext block →recent activity

Analyzing

Block #100,033,652

12 transactions · 12 stateful · 2026-08-28 23:49:47 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,033,652  ·  12 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

0x02373c43…3cb3

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcc

0x34b655…2a6f

4 touches
1 conflict

0x2999ebda…ce6c

0x34b655…2a6f

2 touches
0 conflicts

0x5f46663c…b4c2

0x34b655…2a6f

2 touches
0 conflicts

0x85a88798…f85e

0x34b655…2a6f

2 touches
0 conflicts

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 0x02373c432b…ff3cb3

← previous block·next block →recent activity