← previous blocknext block →recent activity

Analyzing

Block #74,466,650

36 transactions · 22 stateful · 2026-05-14 04:42:23 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,466,650  ·  36 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x861ebd0d…57fb

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x91ecc547…33ef

0x1b6862…e19c

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

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 0x861ebd0db0…6157fb

← previous block·next block →recent activity