← previous blocknext block →recent activity

Analyzing

Block #74,040,347

13 transactions · 9 stateful · 2026-05-12 05:26:08 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,347  ·  13 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

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xe4d7c4d4…956c

0x065c9d…c394

3 touches
1 conflict

0x55c362ef…9329

0xd32edf…ff58

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

1 conflict on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity