← previous blocknext block →recent activity

Analyzing

Block #73,046,266

27 transactions · 17 stateful · 2026-05-07 14:52:29 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,046,266  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xae9df9df…ecda

0xd32edf…ff58

9 touches
10 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x227d6364…2d79

0x065c9d…c394

5 touches
3 conflicts

0x04dc4440…5cb0

0x065c9d…c394

5 touches
3 conflicts

0x00000000…000b

0x6ca43f…c331

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 0xae9df9df82…d6ecda

← previous block·next block →recent activity