← previous blocknext block →recent activity

Analyzing

Block #93,389,896

30 transactions · 20 stateful · 2026-08-05 16:04:03 UTC

Parallelism

90/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,389,896  ·  30 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xc824469a…641e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xe92e43cc…a4cc

0x34b655…2a6f

6 touches
3 conflicts

0xecd87a39…d9c5

0x34b655…2a6f

6 touches
3 conflicts

0x9fb7a0df…99e2

0x34b655…2a6f

5 touches
3 conflicts

0x4d3be02f…ed6c

0x34b655…2a6f

5 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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity