← previous blocknext block →recent activity

Analyzing

Block #74,774,607

23 transactions · 17 stateful · 2026-05-15 15:02:52 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,774,607  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0b92712b…7676

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0000

0x81550c…bba7

4 touches
1 conflict

0x00000000…0001

0x81550c…bba7

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 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 0x348fda08cf…fc7e96

← previous block·next block →recent activity