← previous blocknext block →recent activity

Analyzing

Block #74,247,701

21 transactions · 19 stateful · 2026-05-13 04:25:32 UTC

Parallelism

62/100

Blocked

53%

Avg conflicts / tx

1.52

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,247,701  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity