← previous blocknext block →recent activity

Analyzing

Block #73,986,967

41 transactions · 35 stateful · 2026-05-11 23:29:33 UTC

Parallelism

76/100

Blocked

57%

Avg conflicts / tx

1.71

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,986,967  ·  41 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x94f4eab2…673c

0x34b655…2a6f

12 touches
15 conflicts

0x33dd841b…b494

0xd32edf…ff58

11 touches
15 conflicts

0x7ee110ef…8394

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0462262d…a368

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity