← previous blocknext block →recent activity

Analyzing

Block #73,048,170

24 transactions · 24 stateful · 2026-05-07 15:05:11 UTC

Parallelism

79/100

Blocked

58%

Avg conflicts / tx

1.29

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,048,170  ·  24 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0x0335ae80…8414

0x8d66a4…3095

6 touches
3 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity