← previous blocknext block →recent activity

Analyzing

Block #74,353,292

22 transactions · 17 stateful · 2026-05-13 16:07:43 UTC

Parallelism

77/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,353,292  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x55010ec8…ea31

0x34b655…2a6f

4 touches
1 conflict

0x75987a0d…c90b

0x34b655…2a6f

4 touches
1 conflict

0x95e5ee51…5e3e

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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