← previous blocknext block →recent activity

Analyzing

Block #74,450,571

25 transactions · 23 stateful · 2026-05-14 02:55:16 UTC

Parallelism

76/100

Blocked

65%

Avg conflicts / tx

1.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,450,571  ·  25 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x8902ba1f…f4b6

0x34b655…2a6f

10 touches
10 conflicts

0xeb0915f1…c150

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c2

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity