← previous blocknext block →recent activity

Analyzing

Block #74,351,536

31 transactions · 23 stateful · 2026-05-13 15:56:02 UTC

Parallelism

84/100

Blocked

30%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,351,536  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0xd3eb4d04…d398

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x513da9cb…da7a

0x065c9d…c394

3 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity