← previous blocknext block →recent activity

Analyzing

Block #74,425,544

17 transactions · 16 stateful · 2026-05-14 00:08:41 UTC

Parallelism

76/100

Blocked

19%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,425,544  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa34a763c…2b03

0x065c9d…c394

3 touches
1 conflict

0xe8cbdaf8…9463

0x065c9d…c394

3 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 conflicts

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity