← previous blocknext block →recent activity

Analyzing

Block #74,765,224

33 transactions · 21 stateful · 2026-05-15 14:00:01 UTC

Parallelism

85/100

Blocked

62%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,765,224  ·  33 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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x648c2a8f…b2a3

0xd32edf…ff58

5 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity