← previous blocknext block →recent activity

Analyzing

Block #92,697,769

25 transactions · 20 stateful · 2026-08-03 06:01:09 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,697,769  ·  25 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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0f6aef87…8137

0x34b655…2a6f

8 touches
6 conflicts

0x724cd9ff…6684

0x0cc9b2…7777

8 touches
6 conflicts

0x00000000…0008

0x0ea966…0742

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x44ad89ba…cf83

0xe4f6e7…9657

8 touches
6 conflicts

0x724cd9ff…6684

0xe4f6e7…9657

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 0x482471adbb…39122f

← previous block·next block →recent activity