← previous blocknext block →recent activity

Analyzing

Block #74,490,388

12 transactions · 11 stateful · 2026-05-14 07:20:17 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,490,388  ·  12 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

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x348be8ba…1e49

0x065c9d…c394

3 touches
1 conflict

0xcc77b33c…6e87

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0xbb6daa0c…9f5f

0x522705…fcd0

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 0xffe431af56…838faa

← previous block·next block →recent activity