← previous blocknext block →recent activity

Analyzing

Block #73,651,228

38 transactions · 26 stateful · 2026-05-10 09:59:26 UTC

Parallelism

66/100

Blocked

58%

Avg conflicts / tx

2.26

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,651,228  ·  38 txs across 13 waves  ·  depth 13
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

wave w12

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

0x1ebe4fe0…250c

0xd32edf…ff58

25 touches
78 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x14d1bf0e…e09c

0x1b6862…e19c

6 touches
3 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

78 conflicts on slot 0x1ebe4fe020…2e250c

← previous block·next block →recent activity