← previous blocknext block →recent activity

Analyzing

Block #73,693,382

31 transactions · 26 stateful · 2026-05-10 14:43:49 UTC

Parallelism

74/100

Blocked

54%

Avg conflicts / tx

1.23

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,693,382  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc9e97522…3519

0x2a68ba…90c5

10 touches
10 conflicts

0xc324a5bd…7d9c

0xd32edf…ff58

9 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0x6ea8fa8d…3dd8

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity