← previous blocknext block →recent activity

Analyzing

Block #73,920,917

39 transactions · 25 stateful · 2026-05-11 16:09:04 UTC

Parallelism

67/100

Blocked

64%

Avg conflicts / tx

2.26

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,920,917  ·  39 txs across 13 waves  ·  depth 13
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

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

0x8ac8b1a8…3a9c

0xd32edf…ff58

25 touches
78 conflicts

0x9c214fd7…a680

0x754704…b603

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0xcd4a0041…2169

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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

78 conflicts on slot 0x8ac8b1a88f…703a9c

← previous block·next block →recent activity