← previous blocknext block →recent activity

Analyzing

Block #74,455,359

26 transactions · 14 stateful · 2026-05-14 03:27:12 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,455,359  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xae53da2b…9f61

0xd32edf…ff58

9 touches
10 conflicts

0x56a919c4…ab49

0xe7cd86…c82d

8 touches
6 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0xe8adf936…34b1

0x188d58…ea8e

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xe8adf936…34b3

0x188d58…ea8e

4 touches
1 conflict

0xf60bb017…fc20

0x188d58…ea8e

4 touches
1 conflict

0xf60bb017…fc21

0x188d58…ea8e

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

10 conflicts on slot 0xae53da2ba7…509f61

← previous block·next block →recent activity