← previous blocknext block →recent activity

Analyzing

Block #99,485,336

26 transactions · 25 stateful · 2026-08-27 01:35:55 UTC

Parallelism

65/100

Blocked

52%

Avg conflicts / tx

1.5

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,485,336  ·  26 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x0dd3d3cd…7281

0x34b655…2a6f

6 touches
3 conflicts

0xb1856468…e84f

0x34b655…2a6f

6 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…00c9

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity