← previous blocknext block →recent activity

Analyzing

Block #73,643,337

15 transactions · 9 stateful · 2026-05-10 09:06:18 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,643,337  ·  15 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

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf6d1f164…77b0

0x34b655…2a6f

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x689cd5fd…5556

0x34b655…2a6f

2 touches
0 conflicts

0x85a88798…f85e

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8a2657f5c3…4ce008

← previous block·next block →recent activity