← previous blocknext block →recent activity

Analyzing

Block #73,338,528

29 transactions · 17 stateful · 2026-05-08 23:16:54 UTC

Parallelism

62/100

Blocked

65%

Avg conflicts / tx

2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,338,528  ·  29 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

0xecfb03f9…d17f

0xd32edf…ff58

21 touches
55 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0x5dfa485c…cf52

0x754704…b603

2 touches
0 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

2 touches
0 conflicts

0x00000000…0000

0x094452…0a09

2 touches
0 conflicts

0x00000000…0002

0x094452…0a09

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

55 conflicts on slot 0xecfb03f9be…b3d17f

← previous block·next block →recent activity