← previous blocknext block →recent activity

Analyzing

Block #73,438,037

11 transactions · 11 stateful · 2026-05-09 10:19:00 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,438,037  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x1c3d4f13…9f90

0x065c9d…c394

2 touches
0 conflicts

0x23eaa3d7…4039

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0xd2b19345…a931

0x065c9d…c394

2 touches
0 conflicts

0x8886a9df…a9c9

0x188d58…ea8e

2 touches
0 conflicts

0x51087f5a…61f7

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity