← previous blocknext block →recent activity

Analyzing

Block #74,774,149

23 transactions · 18 stateful · 2026-05-15 14:59:50 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,774,149  ·  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

8 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x29abd9db…3038

0xd32edf…ff58

3 touches
1 conflict

0x11f25e19…8bb1

0x34b655…2a6f

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

6 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity