← previous blocknext block →recent activity

Analyzing

Block #74,260,162

10 transactions · 8 stateful · 2026-05-13 05:48:18 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,260,162  ·  10 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

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x9ef83c66…4437

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0x56a064ab…6c7d

0x34b655…2a6f

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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 0x8db1e0f2ad…b02fcf

← previous block·next block →recent activity