← previous blocknext block →recent activity

Analyzing

Block #73,014,037

35 transactions · 30 stateful · 2026-05-07 11:17:58 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,014,037  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xac32697c…8d45

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0xac32697c6e…078d45

← previous block·next block →recent activity