← previous blocknext block →recent activity

Analyzing

Block #99,859,437

28 transactions · 24 stateful · 2026-08-28 09:12:09 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,859,437  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xccdcfcbc…c7a0

0x34b655…2a6f

14 touches
21 conflicts

0xc284775a…bbd4

0x34b655…2a6f

10 touches
10 conflicts

0xa169711f…c7f3

0x34b655…2a6f

10 touches
10 conflicts

0x014e90b3…470f

0x34b655…2a6f

10 touches
10 conflicts

0xba062f97…bf75

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xa242e227…2e45

0x34b655…2a6f

6 touches
3 conflicts

0x044844a0…7418

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

21 conflicts on slot 0xccdcfcbcba…3cc7a0

← previous block·next block →recent activity