← previous blocknext block →recent activity

Analyzing

Block #74,351,921

32 transactions · 23 stateful · 2026-05-13 15:58:36 UTC

Parallelism

78/100

Blocked

30%

Avg conflicts / tx

0.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,351,921  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x98f0dd32…79b3

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x552007fb…31b7

0x065c9d…c394

3 touches
1 conflict

0xef138727…06f1

0x065c9d…c394

3 touches
1 conflict

0x661d0af9…84dd

0x065c9d…c394

3 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

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: 0xd32edf66…9fff58

10 conflicts on slot 0x98f0dd32c7…2279b3

← previous block·next block →recent activity