← previous blocknext block →recent activity

Analyzing

Block #73,660,450

24 transactions · 21 stateful · 2026-05-10 11:01:32 UTC

Parallelism

46/100

Blocked

76%

Avg conflicts / tx

2.46

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,660,450  ·  24 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

0x00000000…003d

0x065c9d…c394

16 touches
28 conflicts

0x72ca0a7a…53e4

0xd32edf…ff58

13 touches
21 conflicts

0xb159af88…a9e7

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

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: 0x065c9d28…a9c394

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity