← previous blocknext block →recent activity

Analyzing

Block #74,773,185

16 transactions · 12 stateful · 2026-05-15 14:53:22 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,773,185  ·  16 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc1497c75…38de

0xd32edf…ff58

3 touches
1 conflict

0x2bc1fe5b…81c5

0x065c9d…c394

2 touches
0 conflicts

0xfb973092…b6f6

0x065c9d…c394

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a994

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: 0x065c9d28…a9c394

3 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity