← previous blocknext block →recent activity

Analyzing

Block #74,761,257

7 transactions · 7 stateful · 2026-05-15 13:33:26 UTC

Parallelism

43/100

Blocked

57%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xf90ba4b4…6fa0

0x34b655…2a6f

4 touches
1 conflict

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x9a291a56…9a9c

0x34b655…2a6f

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity