← previous blocknext block →recent activity

Analyzing

Block #74,388,962

14 transactions · 10 stateful · 2026-05-13 20:05:10 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,388,962  ·  14 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

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x5d70606a…1d53

0x34b655…2a6f

2 touches
0 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

2 touches
0 conflicts

0x9b36f19f…fa5a

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

1 conflict on slot 0xa3ff1ab2e8…2a8ae3

← previous block·next block →recent activity