← previous blocknext block →recent activity

Analyzing

Block #74,628,954

14 transactions · 11 stateful · 2026-05-14 22:50:25 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,628,954  ·  14 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

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x9074e40a…df3f

0xd32edf…ff58

3 touches
1 conflict

0xd6a2705a…24e8

0x065c9d…c394

3 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x9194f4a3…10b8

0x754704…b603

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