← previous blocknext block →recent activity

Analyzing

Block #74,761,159

25 transactions · 16 stateful · 2026-05-15 13:32:46 UTC

Parallelism

84/100

Blocked

31%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,761,159  ·  25 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

0xffaf34a8…5ef2

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

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: 0xd32edf66…9fff58

3 conflicts on slot 0xffaf34a88b…f55ef2

← previous block·next block →recent activity