← previous blocknext block →recent activity

Analyzing

Block #74,502,666

15 transactions · 13 stateful · 2026-05-14 08:42:06 UTC

Parallelism

87/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,502,666  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x21d8e673…067d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…00001c

← previous block·next block →recent activity