← previous blocknext block →recent activity

Analyzing

Block #74,289,048

9 transactions · 7 stateful · 2026-05-13 09:00:24 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,289,048  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xdf7899c0…c53a

0x34b655…2a6f

4 touches
1 conflict

0x29dfc70a…7e09

0x34b655…2a6f

2 touches
0 conflicts

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x5d70606a…1d53

0x34b655…2a6f

2 touches
0 conflicts

0x6423a16a…fff4

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 0x5de96bd34a…ecc60c

← previous block·next block →recent activity