← previous blocknext block →recent activity

Analyzing

Block #74,527,267

17 transactions · 15 stateful · 2026-05-14 11:27:49 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,527,267  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x9deb699a…c246

0xd32edf…ff58

5 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2df045f1…2bbc

0x065c9d…c394

4 touches
1 conflict

0xb4d54ad0…b782

0x065c9d…c394

3 touches
1 conflict

0xc6deb2a9…7a1f

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 0x0000000000…00003d

← previous block·next block →recent activity