← previous blocknext block →recent activity

Analyzing

Block #74,651,076

10 transactions · 8 stateful · 2026-05-15 01:17:43 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,651,076  ·  10 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

0xe7b43a2a…c7f5

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x9910453f…9dc5

0x065c9d…c394

3 touches
1 conflict

0x1ca7a2ef…404f

0x065c9d…c394

3 touches
1 conflict

0x317f6232…8a4c

0x065c9d…c394

3 touches
1 conflict

0x7a4f77c8…a2a0

0x065c9d…c394

3 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x2e2214a9…fe0d

0x5d823e…89c6

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 0xe7b43a2a10…99c7f5

← previous block·next block →recent activity