← previous blocknext block →recent activity

Analyzing

Block #73,598,680

40 transactions · 34 stateful · 2026-05-10 04:07:10 UTC

Parallelism

75/100

Blocked

65%

Avg conflicts / tx

1.57

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,598,680  ·  40 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xbede6522…8d0a

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0xe01158fd…f97e

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

10 touches
10 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

21 conflicts on slot 0xbede652225…6b8d0a

← previous block·next block →recent activity