← previous blocknext block →recent activity

Analyzing

Block #73,837,623

18 transactions · 13 stateful · 2026-05-11 06:53:58 UTC

Parallelism

78/100

Blocked

54%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,837,623  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x8d47c9a4…f121

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc75f0518…3706

0xd32edf…ff58

7 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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…00001f

← previous block·next block →recent activity