← previous blocknext block →recent activity

Analyzing

Block #74,389,062

14 transactions · 11 stateful · 2026-05-13 20:05:50 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,389,062  ·  14 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

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x76e559a4…77fb

0x2a68ba…90c5

4 touches
1 conflict

0x77941ed1…bd0f

0x065c9d…c394

3 touches
1 conflict

0x8ce1c145…7cfb

0x065c9d…c394

3 touches
1 conflict

0x4e70fe41…daf6

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

1 conflict on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity