← previous blocknext block →recent activity

Analyzing

Block #99,480,944

20 transactions · 20 stateful · 2026-08-27 01:13:48 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

2.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,480,944  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd814f518…f5b4

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x949b4d5a…f23c

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
4 conflicts

0x6771eae2…7014

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

28 conflicts on slot 0xd814f51828…c6f5b4

← previous block·next block →recent activity