← previous blocknext block →recent activity

Analyzing

Block #74,351,977

35 transactions · 31 stateful · 2026-05-13 15:58:58 UTC

Parallelism

80/100

Blocked

55%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,351,977  ·  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

0x98160195…1d1f

0xd32edf…ff58

13 touches
21 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf35dca9e…bd89

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

21 conflicts on slot 0x9816019552…1b1d1f

← previous block·next block →recent activity