← previous blocknext block →recent activity

Analyzing

Block #74,311,842

9 transactions · 8 stateful · 2026-05-13 11:32:11 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,311,842  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0x6ae53523…2c70

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x556d9ba7…f8a1

0x065c9d…c394

4 touches
1 conflict

0xf6ecd6ae…f0ca

0x065c9d…c394

3 touches
1 conflict

0x287163e2…fc37

0x065c9d…c394

3 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: 0x065c9d28…a9c394

3 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity