← previous blocknext block →recent activity

Analyzing

Block #99,160,809

21 transactions · 16 stateful · 2026-08-25 22:22:24 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,160,809  ·  21 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

0xe1c4e5ce…0dec

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

8 touches
6 conflicts

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x24a3c140…d173

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xe1c4e5ce15…770dec

← previous block·next block →recent activity