← previous blocknext block →recent activity

Analyzing

Block #74,351,538

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

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,351,538  ·  12 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

0xa066e0f0…e59f

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x5ffc25fa…b119

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x6bb22c06…c9de

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

3 conflicts on slot 0xa066e0f0f1…27e59f

← previous block·next block →recent activity