← previous blocknext block →recent activity

Analyzing

Block #74,593,957

23 transactions · 12 stateful · 2026-05-14 18:56:23 UTC

Parallelism

87/100

Blocked

42%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,593,957  ·  23 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

0xffa6c6aa…9824

0xd32edf…ff58

5 touches
3 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

3 conflicts on slot 0xffa6c6aa28…3b9824

← previous block·next block →recent activity