← previous blocknext block →recent activity

Analyzing

Block #99,503,089

19 transactions · 19 stateful · 2026-08-27 03:05:17 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

1.26

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,503,089  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0x886db264…846e

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0x2ce2d49e…d185

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity