← previous blocknext block →recent activity

Analyzing

Block #74,956,944

9 transactions · 9 stateful · 2026-05-16 11:20:04 UTC

Parallelism

56/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,956,944  ·  9 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

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x50c57726…98cb

0xd32edf…ff58

3 touches
1 conflict

0x0aba8932…1aae

0x065c9d…c394

3 touches
1 conflict

0x3b8fbace…4160

0x065c9d…c394

3 touches
1 conflict

0x35600127…667b

0x065c9d…c394

3 touches
1 conflict

0x01a89030…f786

0x368ee5…7ca4

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

6 conflicts on slot 0xba38536db1…342b7d

← previous block·next block →recent activity