← previous blocknext block →recent activity

Analyzing

Block #73,649,528

11 transactions · 8 stateful · 2026-05-10 09:48:02 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,649,528  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x119d3f42…8e26

0x34b655…2a6f

2 touches
0 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

2 touches
0 conflicts

0x462d8e25…1e49

0x34b655…2a6f

2 touches
0 conflicts

0x543dc30d…2a82

0x34b655…2a6f

2 touches
0 conflicts

0x7da7cd6a…e910

0x34b655…2a6f

2 touches
0 conflicts

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity