← previous blocknext block →recent activity

Analyzing

Block #74,458,662

37 transactions · 30 stateful · 2026-05-14 03:49:12 UTC

Parallelism

81/100

Blocked

67%

Avg conflicts / tx

1.49

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,458,662  ·  37 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

0x1c389468…6b0e

0x34b655…2a6f

14 touches
21 conflicts

0xe26cf477…6f4f

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x84d7a5ea…06dc

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c3

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: 0x34b6552d…112a6f

21 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity