← previous blocknext block →recent activity

Analyzing

Block #73,041,778

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

Parallelism

81/100

Blocked

59%

Avg conflicts / tx

1.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…0002

0xd574ca…7ab1

14 touches
21 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0x7f189cf6…afab

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xccb9b3a9…03a7

0xd32edf…ff58

7 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x8048bd0f…5893

0x065c9d…c394

5 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: 0xd574cae5…037ab1

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity