← previous blocknext block →recent activity

Analyzing

Block #73,918,422

26 transactions · 18 stateful · 2026-05-11 15:52:27 UTC

Parallelism

58/100

Blocked

67%

Avg conflicts / tx

1.31

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,918,422  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 conflicts

0xba817a07…c8ce

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x0f94ee4c…1898

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity