← previous blocknext block →recent activity

Analyzing

Block #74,409,493

11 transactions · 10 stateful · 2026-05-13 22:21:54 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,409,493  ·  11 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x7b98cb15…f523

0x065c9d…c394

3 touches
1 conflict

0x8ad10a4a…9d86

0x065c9d…c394

3 touches
1 conflict

0xd2abff8e…2b62

0x065c9d…c394

3 touches
1 conflict

0xf45ca56b…a0cf

0x065c9d…c394

3 touches
1 conflict

0x4dc2b5d5…9896

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity