← previous blocknext block →recent activity

Analyzing

Block #73,804,733

42 transactions · 32 stateful · 2026-05-11 03:15:05 UTC

Parallelism

64/100

Blocked

75%

Avg conflicts / tx

2.4

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #73,804,733  ·  42 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0xc47878c9…863b

0xd32edf…ff58

17 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x99120c08…ee84

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xe8a35d5a…cb9d

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0xc47878c902…17863b

← previous block·next block →recent activity