← previous blocknext block →recent activity

Analyzing

Block #73,677,778

19 transactions · 15 stateful · 2026-05-10 12:58:39 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.37

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,677,778  ·  19 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

0x82df2620…6a7c

0xd32edf…ff58

13 touches
21 conflicts

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0xe7673bb9…3055

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0005

0x5e60bc…fe22

4 touches
1 conflict

0x6a10e793…2469

0x5e60bc…fe22

4 touches
1 conflict

0x424f8fd0…4fcf

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

21 conflicts on slot 0x82df262063…f36a7c

← previous block·next block →recent activity