← previous blocknext block →recent activity

Analyzing

Block #74,750,730

29 transactions · 20 stateful · 2026-05-15 12:22:47 UTC

Parallelism

76/100

Blocked

55%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,750,730  ·  29 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

0xe26262ec…dac0

0xd32edf…ff58

13 touches
21 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x2965e2d6…5800

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

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

21 conflicts on slot 0xe26262ec1b…7adac0

← previous block·next block →recent activity