← previous blocknext block →recent activity

Analyzing

Block #73,922,556

20 transactions · 19 stateful · 2026-05-11 16:19:58 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

1.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,922,556  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xcbd51f79…fff1

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0029

0x1b6862…e19c

10 touches
10 conflicts

0xd5b10148…e632

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity