← previous blocknext block →recent activity

Analyzing

Block #94,815,527

27 transactions · 24 stateful · 2026-08-10 15:51:06 UTC

Parallelism

63/100

Blocked

54%

Avg conflicts / tx

1.67

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,815,527  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x734ee320…caae

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x3e3d473b…017e

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x772ab420…c2f6

0x34b655…2a6f

8 touches
6 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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

15 conflicts on slot 0x734ee32053…cecaae

← previous block·next block →recent activity