← previous blocknext block →recent activity

Analyzing

Block #73,867,330

13 transactions · 10 stateful · 2026-05-11 10:12:06 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,867,330  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa385f20d…74c3

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x98067f20…59e3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x81955a0a…29ee

0x6657d1…8ccc

4 touches
1 conflict

0xeeb8b7fc…24d6

0x6657d1…8ccc

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

6 conflicts on slot 0xa385f20d3b…5f74c3

← previous block·next block →recent activity