← previous blocknext block →recent activity

Analyzing

Block #74,906,573

16 transactions · 14 stateful · 2026-05-16 05:43:11 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,906,573  ·  16 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

0xdce1361d…36d1

0x065c9d…c394

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x09c865d3…44c3

0x065c9d…c394

3 touches
1 conflict

0x6f3912be…6c40

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x9cafc3b6…ee8c

0x000000…012a

2 touches
0 conflicts

0x62e20208…be65

0x0555e3…2b9c

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 0xdce1361d0f…e336d1

← previous block·next block →recent activity