← previous blocknext block →recent activity

Analyzing

Block #73,041,789

36 transactions · 28 stateful · 2026-05-07 14:22:38 UTC

Parallelism

86/100

Blocked

68%

Avg conflicts / tx

1.14

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,041,789  ·  36 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xf4730a2d…3538

0x34b655…2a6f

10 touches
10 conflicts

0xbb334430…560e

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x6aa624fd…a852

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity