← previous blocknext block →recent activity

Analyzing

Block #73,660,857

30 transactions · 23 stateful · 2026-05-10 11:04:19 UTC

Parallelism

67/100

Blocked

52%

Avg conflicts / tx

1.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,660,857  ·  30 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

0x5730be1a…78af

0xd32edf…ff58

13 touches
21 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

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

21 conflicts on slot 0x5730be1a04…5f78af

← previous block·next block →recent activity