← previous blocknext block →recent activity

Analyzing

Block #99,587,943

17 transactions · 17 stateful · 2026-08-27 10:15:19 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,587,943  ·  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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x53c41998…7d52

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4ee66471…90b5

0x34b655…2a6f

4 touches
1 conflict

0x53ca1284…cb2c

0x34b655…2a6f

4 touches
1 conflict

0x69b6f46c…d6b2

0x34b655…2a6f

4 touches
1 conflict

0x8b780b26…f5ff

0x34b655…2a6f

4 touches
1 conflict

0x907f87f3…9efb

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 0xc824469a90…af6425

← previous block·next block →recent activity