← previous blocknext block →recent activity

Analyzing

Block #74,197,082

9 transactions · 7 stateful · 2026-05-12 22:49:01 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,197,082  ·  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

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x71e4ffd1…9beb

0x34b655…2a6f

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x60a42a5e…9da2

0x34b655…2a6f

4 touches
1 conflict

0x1e945229…691a

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

0x34b655…2a6f

4 touches
1 conflict

0x2bf5cf4b…2f5b

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity