← previous blocknext block →recent activity

Analyzing

Block #73,170,612

22 transactions · 16 stateful · 2026-05-08 04:39:29 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,170,612  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0829711c…8e7d

0xd32edf…ff58

9 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x9c11d943…f33a

0x0555e3…2b9c

2 touches
0 conflicts

0x8df008ec…ffcf

0x065c9d…c394

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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: 0xd32edf66…9fff58

10 conflicts on slot 0x0829711c44…c98e7d

← previous block·next block →recent activity