← previous blocknext block →recent activity

Analyzing

Block #99,476,262

19 transactions · 18 stateful · 2026-08-27 00:50:11 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,476,262  ·  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

8 touches
6 conflicts

0xb1856468…e84f

0x34b655…2a6f

8 touches
6 conflicts

0x5f88acf6…d385

0x34b655…2a6f

6 touches
3 conflicts

0x2c2761c0…476e

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x8b780b26…f5ff

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity