← previous blocknext block →recent activity

Analyzing

Block #73,502,304

20 transactions · 17 stateful · 2026-05-09 17:26:45 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,502,304  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3dc7861b…1dd1

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x7353e6be…a0c8

0x065c9d…c394

2 touches
0 conflicts

0xa41123fa…60f2

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0xd32edf66…9fff58

28 conflicts on slot 0x3dc7861b9d…651dd1

← previous block·next block →recent activity