← previous blocknext block →recent activity

Analyzing

Block #73,816,906

17 transactions · 14 stateful · 2026-05-11 04:36:06 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,816,906  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x552a496a…c24c

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x91220b8f…7a08

0x1b6862…e19c

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4ca337de…69b6

0x065c9d…c394

4 touches
1 conflict

0xff360154…ef1e

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

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 0x552a496a95…ebc24c

← previous block·next block →recent activity