← previous blocknext block →recent activity

Analyzing

Block #74,742,641

14 transactions · 6 stateful · 2026-05-15 11:28:49 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,742,641  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0a6c34ee…b907

0x065c9d…c394

4 touches
1 conflict

0x435befcf…e380

0x065c9d…c394

3 touches
1 conflict

0xa5516df2…3ca0

0x065c9d…c394

3 touches
1 conflict

0x319eef8e…07dd

0x065c9d…c394

2 touches
0 conflicts

0xbc3491b8…1e9b

0x065c9d…c394

2 touches
0 conflicts

0xc87c00f2…474d

0x065c9d…c394

2 touches
0 conflicts

0xd8e25e5d…0bc4

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

1 conflict on slot 0x0a6c34eead…3ab907

← previous block·next block →recent activity