← previous blocknext block →recent activity

Analyzing

Block #74,502,651

20 transactions · 13 stateful · 2026-05-14 08:42:00 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,502,651  ·  20 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

0x4686ddd1…a8e7

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x44ad89ba…cf83

0x0cc9b2…7777

4 touches
1 conflict

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0xa10c86f8…4b74

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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

6 conflicts on slot 0x4686ddd120…0ba8e7

← previous block·next block →recent activity