← previous blocknext block →recent activity

Analyzing

Block #74,356,654

18 transactions · 18 stateful · 2026-05-13 16:30:09 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,356,654  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x55888ede…6745

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity