← previous blocknext block →recent activity

Analyzing

Block #74,506,884

21 transactions · 19 stateful · 2026-05-14 09:10:31 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,506,884  ·  21 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…0002

0xab3526…fa38

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x1c348b58…836a

0x34b655…2a6f

2 touches
0 conflicts

0x220f4f84…15f8

0x34b655…2a6f

2 touches
0 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

2 touches
0 conflicts

0x55888ede…6745

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity