← previous blocknext block →recent activity

Analyzing

Block #73,651,799

40 transactions · 29 stateful · 2026-05-10 10:03:15 UTC

Parallelism

88/100

Blocked

45%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,651,799  ·  40 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

0xf2438038…5fa7

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xda68c75f…2912

0x34b655…2a6f

8 touches
6 conflicts

0xdd11cc1a…2b02

0xd32edf…ff58

7 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

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: 0x34b6552d…112a6f

10 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity