← previous blocknext block →recent activity

Analyzing

Block #74,597,353

25 transactions · 12 stateful · 2026-05-14 19:19:09 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.28

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,597,353  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0x59ef13ba…2741

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

2 touches
0 conflicts

0xa91c899f…6ee3

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity