← previous blocknext block →recent activity

Analyzing

Block #73,811,416

18 transactions · 14 stateful · 2026-05-11 03:59:38 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,811,416  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x33a9cf32…3c77

0xd32edf…ff58

9 touches
10 conflicts

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0x2ce2d49e…d18c

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x3577138e…6c47

0x065c9d…c394

5 touches
3 conflicts

0xa980598e…ec52

0x3bd359…433a

4 touches
1 conflict

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 0x33a9cf32ba…483c77

← previous block·next block →recent activity