← previous blocknext block →recent activity

Analyzing

Block #73,034,241

38 transactions · 23 stateful · 2026-05-07 13:32:26 UTC

Parallelism

89/100

Blocked

39%

Avg conflicts / tx

0.34

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,034,241  ·  38 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

0xb28aee23…6d39

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0xd574ca…7ab1

6 touches
3 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0000

0x776059…1d8d

4 touches
1 conflict

0x00000000…0001

0x776059…1d8d

4 touches
1 conflict

0x44ad89ba…cf83

0xde22b2…7777

4 touches
1 conflict

0x00000000…001f

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

6 conflicts on slot 0xb28aee23b7…de6d39

← previous block·next block →recent activity