← previous blocknext block →recent activity

Analyzing

Block #74,654,511

13 transactions · 9 stateful · 2026-05-15 01:40:46 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,654,511  ·  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

0xf96ece64…fcab

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xa58cd239…269c

0x065c9d…c394

3 touches
1 conflict

0xb218490f…fc95

0x065c9d…c394

3 touches
1 conflict

0xd2060263…aa84

0x065c9d…c394

2 touches
0 conflicts

0xf8b624c0…bebc

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xf96ece6436…21fcab

← previous block·next block →recent activity