← previous blocknext block →recent activity

Analyzing

Block #74,958,670

9 transactions · 5 stateful · 2026-05-16 11:31:43 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,958,670  ·  9 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

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2fad73a1…ae09

0x34b655…2a6f

4 touches
1 conflict

0x5d4a7696…13d9

0x34b655…2a6f

2 touches
0 conflicts

0x97e4c862…4419

0x34b655…2a6f

2 touches
0 conflicts

0x9c83a7b1…e305

0x34b655…2a6f

2 touches
0 conflicts

0xa9988419…9f45

0x34b655…2a6f

2 touches
0 conflicts

0xbe393acf…b8ec

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity