← previous blocknext block →recent activity

Analyzing

Block #74,471,575

13 transactions · 12 stateful · 2026-05-14 05:15:03 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,471,575  ·  13 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0xc9a9747f…e622

0x34b655…2a6f

4 touches
1 conflict

0x05e5ce66…b69d

0x2880ab…7b43

2 touches
0 conflicts

0x0cfb5d79…7ccb

0x2880ab…7b43

2 touches
0 conflicts

0x0cfb5d79…7ccc

0x2880ab…7b43

2 touches
0 conflicts

0x12117fd0…ec1a

0x2880ab…7b43

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity