← previous blocknext block →recent activity

Analyzing

Block #74,650,987

11 transactions · 10 stateful · 2026-05-15 01:17:08 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,650,987  ·  11 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x08f2c0e7…7be7

0x34b655…2a6f

2 touches
0 conflicts

0x0ac81f35…832c

0x34b655…2a6f

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x15e313f3…9aa1

0x34b655…2a6f

2 touches
0 conflicts

0x2168a9fd…8ce0

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity