← previous blocknext block →recent activity

Analyzing

Block #73,043,177

22 transactions · 17 stateful · 2026-05-07 14:31:54 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,043,177  ·  22 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

0xb3e3f988…c785

0xd32edf…ff58

9 touches
10 conflicts

0x3bd55803…5d4f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

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

10 conflicts on slot 0xb3e3f98877…24c785

← previous block·next block →recent activity