← previous blocknext block →recent activity

Analyzing

Block #74,406,909

21 transactions · 19 stateful · 2026-05-13 22:04:41 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,406,909  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x00131e96…2ba9

0x5afd3e…7620

2 touches
0 conflicts

0x3009543e…4d66

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0006

0x60bb42…87ea

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity