← previous blocknext block →recent activity

Analyzing

Block #73,493,277

37 transactions · 28 stateful · 2026-05-09 16:26:39 UTC

Parallelism

68/100

Blocked

61%

Avg conflicts / tx

2.11

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,493,277  ·  37 txs across 12 waves  ·  depth 12
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

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

0x04cd8e06…8329

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x0a85a226…83ba

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

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: 0xd32edf66…9fff58

66 conflicts on slot 0x04cd8e060f…6b8329

← previous block·next block →recent activity