← previous blocknext block →recent activity

Analyzing

Block #74,346,410

19 transactions · 14 stateful · 2026-05-13 15:22:02 UTC

Parallelism

84/100

Blocked

21%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,410  ·  19 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x8a8dc9e2…2962

0x5afd3e…7620

2 touches
0 conflicts

0xd2d6fd22…a0f2

0x5afd3e…7620

2 touches
0 conflicts

0x02e953d1…f2b7

0x5c2513…7777

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity