← previous blocknext block →recent activity

Analyzing

Block #99,820,665

16 transactions · 16 stateful · 2026-08-28 05:56:03 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,820,665  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x230d0904…a656

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xb38b444a…f83c

0x34b655…2a6f

6 touches
3 conflicts

0xe108b282…58b3

0x34b655…2a6f

6 touches
3 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x46611d8f…8963

0x34b655…2a6f

4 touches
1 conflict

0x886db264…846e

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

6 conflicts on slot 0x230d09044b…3aa656

← previous block·next block →recent activity