← previous blocknext block →recent activity

Analyzing

Block #74,457,109

21 transactions · 16 stateful · 2026-05-14 03:38:52 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,457,109  ·  21 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

0x0468fa92…8884

0xd32edf…ff58

5 touches
3 conflicts

0x269c9f42…7a5d

0x34b655…2a6f

4 touches
1 conflict

0x116a621e…f97f

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

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: 0xd32edf66…9fff58

3 conflicts on slot 0x0468fa92c4…3e8884

← previous block·next block →recent activity