← previous blocknext block →recent activity

Analyzing

Block #74,304,649

10 transactions · 6 stateful · 2026-05-13 10:44:17 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,304,649  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe1f1dcce…a0ce

0x065c9d…c394

4 touches
1 conflict

0x0ceb5297…a9af

0x065c9d…c394

3 touches
1 conflict

0x3d22b07d…0d78

0x065c9d…c394

2 touches
0 conflicts

0x7f9db8be…f93e

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x2e2214a9…fe0d

0x5d823e…89c6

2 touches
0 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

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 0x0000000000…00003d

← previous block·next block →recent activity