← previous blocknext block →recent activity

Analyzing

Block #74,510,228

14 transactions · 13 stateful · 2026-05-14 09:33:00 UTC

Parallelism

71/100

Blocked

23%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,510,228  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xba85143e…a3e5

0x34b655…2a6f

4 touches
1 conflict

0xa9920735…2215

0x0c65a0…0852

2 touches
0 conflicts

0x61519463…c24a

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0000

0x6b405d…1c7c

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