← previous blocknext block →recent activity

Analyzing

Block #73,261,066

38 transactions · 32 stateful · 2026-05-08 14:41:27 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.53

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,261,066  ·  38 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xaf635590…cd35

0xd32edf…ff58

15 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

6 touches
3 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 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 0xaf6355906d…73cd35

← previous block·next block →recent activity