← previous blocknext block →recent activity

Analyzing

Block #74,404,864

11 transactions · 10 stateful · 2026-05-13 21:51:05 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,404,864  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xfa40e0ae…12f0

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xfac61869…a55d

0x1b6862…e19c

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity