← previous blocknext block →recent activity

Analyzing

Block #74,040,713

12 transactions · 11 stateful · 2026-05-12 05:28:33 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,040,713  ·  12 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

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x919ee14a…c413

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

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 0xdaca243a5e…09f9de

← previous block·next block →recent activity