← previous blocknext block →recent activity

Analyzing

Block #74,770,312

35 transactions · 25 stateful · 2026-05-15 14:34:09 UTC

Parallelism

91/100

Blocked

32%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,770,312  ·  35 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xb138d087…4689

0x34b655…2a6f

4 touches
1 conflict

0xdc683230…6df3

0x34b655…2a6f

4 touches
1 conflict

0x22882eec…bc8a

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

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

← previous block·next block →recent activity