← previous blocknext block →recent activity

Analyzing

Block #73,211,072

12 transactions · 12 stateful · 2026-05-08 09:09:00 UTC

Parallelism

83/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,072  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4ac4a2c2…2707

0x34b655…2a6f

4 touches
1 conflict

0xf4730a2d…3538

0x34b655…2a6f

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba60

0x188d58…ea8e

2 touches
0 conflicts

0x0b873f52…4fde

0x34b655…2a6f

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

2 touches
0 conflicts

0x23f3d725…69f8

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

1 conflict on slot 0x4ac4a2c2e0…f32707

← previous block·next block →recent activity