← previous blocknext block →recent activity

Analyzing

Block #74,033,819

21 transactions · 16 stateful · 2026-05-12 04:42:39 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,033,819  ·  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

0x48a86c5b…b016

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x4d42f16e…a6c9

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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

10 conflicts on slot 0x48a86c5bb0…fdb016

← previous block·next block →recent activity