← previous blocknext block →recent activity

Analyzing

Block #99,210,507

22 transactions · 19 stateful · 2026-08-26 02:32:26 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,210,507  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x06e40499…165e

0x2b46c0…1669

4 touches
1 conflict

0x45f562b2…9294

0x2b46c0…1669

4 touches
1 conflict

0x8488f10f…9353

0x2b46c0…1669

4 touches
1 conflict

0x8488f10f…9354

0x2b46c0…1669

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity