← previous blocknext block →recent activity

Analyzing

Block #74,459,151

35 transactions · 23 stateful · 2026-05-14 03:52:27 UTC

Parallelism

71/100

Blocked

65%

Avg conflicts / tx

1.29

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,459,151  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x0aedbad0…9d3f

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x972da85f…50ae

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

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

36 conflicts on slot 0x0aedbad022…899d3f

← previous block·next block →recent activity