← previous blocknext block →recent activity

Analyzing

Block #74,631,619

25 transactions · 19 stateful · 2026-05-14 23:08:09 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,631,619  ·  25 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

0xaff1652d…a7b5

0xd32edf…ff58

11 touches
15 conflicts

0xf91b744e…9117

0x754704…b603

10 touches
10 conflicts

0xce8bbe33…b72e

0x3bd359…433a

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x0a6cb118…4caa

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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: 0xd32edf66…9fff58

15 conflicts on slot 0xaff1652d45…eca7b5

← previous block·next block →recent activity