← previous blocknext block →recent activity

Analyzing

Block #99,196,289

20 transactions · 18 stateful · 2026-08-26 01:20:55 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,196,289  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x4757fc7b…70b7

0x34b655…2a6f

4 touches
1 conflict

0x4e58deff…c5d0

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x7efbf74f…f9d2

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 0xc824469a90…af6425

← previous block·next block →recent activity