← previous blocknext block →recent activity

Analyzing

Block #99,658,911

24 transactions · 19 stateful · 2026-08-27 16:16:49 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,658,911  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe226a0be…c046

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x50807b43…b4ee

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x9ea1ca97…7b41

0x34b655…2a6f

6 touches
3 conflicts

0xda6b535e…6d6b

0x1b6862…e19c

4 touches
1 conflict

0x0cf0cbef…f0dc

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 0xe226a0be4d…4bc046

← previous block·next block →recent activity