← previous blocknext block →recent activity

Analyzing

Block #74,655,261

13 transactions · 12 stateful · 2026-05-15 01:45:48 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,655,261  ·  13 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

0x80c48b52…56af

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xd18a8dca…4529

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

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 0x80c48b52f2…4856af

← previous block·next block →recent activity