← previous blocknext block →recent activity

Analyzing

Block #74,288,527

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

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,288,527  ·  12 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

0x209d12c9…80e3

0x065c9d…c394

4 touches
1 conflict

0x7a48d54b…aa0c

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x29e1b121…c013

0x065c9d…c394

2 touches
0 conflicts

0x4c44ea98…59af

0x065c9d…c394

2 touches
0 conflicts

0x6dbd4f54…fb26

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x209d12c9eb…6980e3

← previous block·next block →recent activity