← previous blocknext block →recent activity

Analyzing

Block #74,353,287

30 transactions · 15 stateful · 2026-05-13 16:07:41 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,353,287  ·  30 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

0x3dac0c0e…cbf0

0xd32edf…ff58

7 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xe4ea5d7d…6a21

0x065c9d…c394

3 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

6 conflicts on slot 0x3dac0c0e80…43cbf0

← previous block·next block →recent activity