← previous blocknext block →recent activity

Analyzing

Block #99,866,888

20 transactions · 20 stateful · 2026-08-28 09:49:41 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,866,888  ·  20 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xeb59aa82…023e

0x34b655…2a6f

6 touches
3 conflicts

0x9116c17c…e222

0x34b655…2a6f

6 touches
3 conflicts

0xb856d1a1…1f18

0x34b655…2a6f

6 touches
3 conflicts

0x39ccd26a…4654

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

4 touches
2 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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity