← previous blocknext block →recent activity

Analyzing

Block #73,041,787

19 transactions · 15 stateful · 2026-05-07 14:22:37 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,041,787  ·  19 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

0x00000000…0002

0xd574ca…7ab1

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdc56c0c6…005e

0xd32edf…ff58

3 touches
1 conflict

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0xef72b59e…a8f5

0x065c9d…c394

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

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: 0xd574cae5…037ab1

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity