← previous blocknext block →recent activity

Analyzing

Block #74,196,777

35 transactions · 24 stateful · 2026-05-12 22:47:00 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,196,777  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8ba8abb5…5a6c

0xd32edf…ff58

13 touches
21 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

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

21 conflicts on slot 0x8ba8abb5e2…6d5a6c

← previous block·next block →recent activity