← previous blocknext block →recent activity

Analyzing

Block #74,562,929

19 transactions · 16 stateful · 2026-05-14 15:28:37 UTC

Parallelism

84/100

Blocked

25%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,562,929  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x195b037f…e0f6

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1a8

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

4 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: 0x34b6552d…112a6f

3 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity