← previous blocknext block →recent activity

Analyzing

Block #73,049,800

34 transactions · 29 stateful · 2026-05-07 15:16:04 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

1.15

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,049,800  ·  34 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x33a5aa4d…b38b

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

10 touches
10 conflicts

0x8e66da19…66b6

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

15 conflicts on slot 0x33a5aa4d53…25b38b

← previous block·next block →recent activity