← previous blocknext block →recent activity

Analyzing

Block #74,369,219

19 transactions · 15 stateful · 2026-05-13 17:53:43 UTC

Parallelism

84/100

Blocked

27%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,369,219  ·  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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0da53d80…5998

0x065c9d…c394

3 touches
1 conflict

0x0072e025…b865

0xd32edf…ff58

3 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 conflicts

0x06db03a6…4692

0x34b655…2a6f

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity