← previous blocknext block →recent activity

Analyzing

Block #73,694,950

13 transactions · 13 stateful · 2026-05-10 14:54:24 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.62

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,694,950  ·  13 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

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xade2ada8…c261

0x065c9d…c394

2 touches
0 conflicts

0xfe25cf26…1086

0x065c9d…c394

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

2 touches
0 conflicts

0x72a152dd…9fb5

0x16f70c…c3dd

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

3 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity