← previous blocknext block →recent activity

Analyzing

Block #74,565,975

23 transactions · 13 stateful · 2026-05-14 15:49:06 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,565,975  ·  23 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

0x162756dc…0b62

0xd32edf…ff58

9 touches
10 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x0c997bd2…3409

0x010592…1c83

2 touches
0 conflicts

0xa5a8f2fa…a3ec

0x010592…1c83

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

10 conflicts on slot 0x162756dc96…ed0b62

← previous block·next block →recent activity