← previous blocknext block →recent activity

Analyzing

Block #73,660,482

10 transactions · 10 stateful · 2026-05-10 11:01:45 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,660,482  ·  10 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

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4089d428…b018

0x34b655…2a6f

2 touches
0 conflicts

0x4ea5b300…4b78

0x34b655…2a6f

2 touches
0 conflicts

0x4ee0b65a…6d40

0x34b655…2a6f

2 touches
0 conflicts

0x4f3a6b4a…3819

0x34b655…2a6f

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity