← previous blocknext block →recent activity

Analyzing

Block #73,043,089

28 transactions · 21 stateful · 2026-05-07 14:31:19 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,043,089  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xda5dfa60…42ab

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

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

15 conflicts on slot 0xda5dfa609c…e442ab

← previous block·next block →recent activity