← previous blocknext block →recent activity

Analyzing

Block #75,063,820

21 transactions · 19 stateful · 2026-05-16 23:13:59 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,063,820  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0xce8bbe33…b72e

0x3bd359…433a

10 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x68992db3…f2d9

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

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: 0x3bd359c1…15433a

10 conflicts on slot 0x6af306bb1d…092e81

← previous block·next block →recent activity